Borrowing it
Nothing to install: this file belongs to shuymn/gh-mcp. 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/shuymn/gh-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/shuymn/gh-mcpWrote 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/shuymn/gh-mcp/claude-md)<a href="https://agentmods.dev/instructions/shuymn/gh-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/shuymn/gh-mcp/claude-md.svg" alt="Measured on agentmods" 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.00925 | $0.00925 |
| Opus 5 | $0.00463 | $0.00463 |
| Sonnet 5 | $0.00185 | $0.00185 |
| Haiku 4.5 | $0.00093 | $0.00093 |
Grade A, and why
gh-mcp CLAUDE.md scanned grade A with 0 findings 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 8d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is a GitHub CLI extension that runs the github-mcp-server as a bundled binary using the user's existing gh authentication. It automates the process of retrieving GitHub credentials and launching the MCP server process with proper authentication.
Common Development Commands
Build
# Build the extension
go build -o gh-mcp .
# Clean build
go clean && go build -o gh-mcp .
# Cross-platform builds
GOOS=linux GOARCH=amd64 go build -o gh-mcp
GOOS=windows GOARCH=amd64 go build -o gh-mcp.exe
GOOS=darwin GOARCH=amd64 go build -o gh-mcp
Development
# Format code
go fmt ./...
# Vet code for issues
go vet ./...
# Tidy dependencies
go mod tidy
# Install locally as Go binary
go install
# Install as GitHub CLI extension (from project root)
gh extension install .
# Test the extension directly
./gh-mcp
Testing
# Run tests (when tests are added)
go test ./...
# Run tests with coverage
go test -cover ./...
# Run tests verbosely
go test -v ./...
Architecture
The project consists of three main components:
-
Authentication (
auth.go):- Retrieves GitHub credentials from
ghCLI usinggithub.com/cli/go-gh/v2 - Returns host and token for the authenticated user
- Uses dependency injection for testability
- Retrieves GitHub credentials from
-
Bundled Server Runtime (
server.go):- Selects and verifies bundled
github-mcp-serverarchives - Extracts the server binary for the current platform
- Runs
github-mcp-server stdiowith GitHub credentials as environment variables - Manages bidirectional I/O streaming between terminal and server process
- Handles graceful shutdown and cleanup
- Selects and verifies bundled
-
Main Orchestration (
main.go):- Sets up signal handling for Ctrl+C
- Coordinates the authentication and bundled server flow
- Provides user feedback with emoji status messages
- Uses dependency injection for testing
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.
- 8d ago First seen · 118 lines · 925 tokens per session scan A d82bda58d760
gh-mcp CLAUDE.md is an instructions file published in the GitHub repository shuymn/gh-mcp (46 stars, last pushed today), licensed MIT. It adds 925 tokens to every session, about $0.0046 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.