Borrowing it
Nothing to install: this file belongs to scopweb/mcp-go-github. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/scopweb/mcp-go-github/main/AGENTS.mdgit clone --depth 1 https://github.com/scopweb/mcp-go-githubWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/scopweb/mcp-go-github/agents-md)<a href="https://agentmods.dev/instructions/scopweb/mcp-go-github/agents-md"><img src="https://agentmods.dev/badge/instructions/scopweb/mcp-go-github/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/scopweb/mcp-go-github/agents-md"><img src="https://agentmods.dev/badge/instructions/scopweb/mcp-go-github/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01286 | $0.01286 |
| Opus 5.5 | $0.00514 | $0.00514 |
| Sonnet 5.5 | $0.00257 | $0.00257 |
| Haiku 4.5 | $0.00129 | $0.00129 |
Grade B, and why
mcp-go-github AGENTS.md scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
`.env` is gitignored. `.mcp.json` is **not** — never put `GITHUB_TOKEN` there. `safety.json`, `.mcp-backups/`, and `mcp-admin-audit.log*` are gitignored. How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Trust executable sources over README/CLAUDE.md when they disagree. go.mod is Go 1.26.6 and github.com/google/go-github/v88. VERSION is 4.1.0.
Broader product docs: CLAUDE.md, CONTRIBUTING.md, CHANGELOG.md. This file is only what an agent would otherwise get wrong.
Commands
go test ./... # what CI runs
go test ./pkg/git/ -v # one package
go test -race ./... # script/test (stricter than CI)
go build ./... # what CI builds
golangci-lint run # what CI lints (.golangci.yml)
.\compile.bat # Windows binary + VERSION ldflags → github-mcp-server-v4.exe
- Unflagged
go buildreports server version"dev". Release builds injectinternal/server.VersionfromVERSION. script/lintandscript/testare bash. On Windows PowerShell use the commands above, not those scripts.- CI (
.github/workflows/ci.yml):go build ./...→go test ./... -v -timeout 60s→golangci-lintlatest. - PRs: Conventional Commits, update
CHANGELOG.md, no hardcoded paths/tokens.
Do not build with -mod=vendor. vendor/ is stale (go-github/v81); go.mod is v88.
Layout
Custom MCP over stdio JSON-RPC (not mark3labs/mcp-go).
| Path | Role |
|---|---|
cmd/github-mcp-server/main.go |
Flags, clients, stdin loop |
internal/server/ |
Protocol + tool dispatch. No tests here. |
internal/hybrid/ |
Git-first file writes, API fallback |
pkg/git/ |
Local git via exec.Command("git", args...) (no shell) |
pkg/github/, pkg/admin/, pkg/dashboard/ |
GitHub API wrappers |
pkg/safety/ |
Risk map, tokens, validators, audit |
pkg/config/ |
Loads safety.json |
pkg/interfaces/ |
Update this first when adding client methods |
ejemplos_github_repositorios/ and test/security/README.md are leftovers from other projects. Ignore them.
Adding or changing tools
Do not add a new top-level tool if an existing one can take another operation. That 26-tool cap is intentional.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 96 lines · 1,286 tokens per session scan B 7f8cbd3bf939
mcp-go-github AGENTS.md is an instructions file published in the GitHub repository scopweb/mcp-go-github (0 stars, last pushed 2mo ago), licensed MIT. It adds 1,286 tokens to every session, about $0.0051 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.