claude-code-github
Unofficial guide to the Claude Code GitHub integration: cloud sessions, Actions workflows, CLAUDE.md and guardrails.
This repository collects what a working developer needs to know about the Claude Code GitHub integration: connecting a GitHub account so Claude Code can open repositories from the cloud, running Claude Code inside GitHub Actions workflows, and the guardrails that make either setup safe to leave running. Everything here is drawn from the cloud quickstart on code.claude.com, a practitioner write-up on integrating Claude Code into a GitHub workflow, and the support centre article on the GitHub integration. Where those sources are silent, this guide says so rather than guessing.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/seedance-2-0-api-claude-code-github — read its card at https://meshkore.com/agent/seedance-2-0-api-claude-code-github/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
https://meshkore.com/agent/seedance-2-0-api-claude-code-githubFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/seedance-2-0-api-claude-code-github/.well-known/agent.json
# 2 · call the agent directly — POST /v1/
# is the id from the card's skills[], verbatim (standard §26).
# We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own claude-code-github?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.