Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/xihuai18/claude-code-mcp/agents-mdgit clone --depth 1 https://github.com/xihuai18/claude-code-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/xihuai18/claude-code-mcp/agents-md)<a href="https://agentmods.dev/instructions/xihuai18/claude-code-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/xihuai18/claude-code-mcp/agents-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 | $0.03078 | $0.03078 |
| Opus 5 | $0.01539 | $0.01539 |
| Sonnet 5 | $0.00616 | $0.00616 |
| Haiku 4.5 | $0.00308 | $0.00308 |
Grade A, and why
claude-code-mcp AGENTS.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 4d 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 — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Agent Instructions (claude-code-mcp)
This repository is a TypeScript (ESM) MCP server wrapping Claude Agent SDK / Claude Code CLI.
Package: @leo000001/claude-code-mcp.
Assumption: MCP server and client run on the same machine (same platform), via stdio.
Last Updated: 2026-02-27
Document Boundary (Must Read)
This repo intentionally separates execution rules from design details:
| Topic | Primary Doc |
|---|---|
| How to execute work, upgrade flow, required checks | AGENTS.md |
| Architecture internals, field/message mapping, lifecycle details | docs/DESIGN.md |
| End-user usage guide | README.md |
| Release history | CHANGELOG.md |
Non-negotiable dedupe rule:
- Keep
AGENTS.mdaction-oriented. - Keep long parameter tables, message mapping, and protocol deep dives in
docs/DESIGN.md. - If details are needed, link to DESIGN anchors instead of duplicating.
Visibility rule for MCP-facing guidance:
- Do not assume MCP-connected coding agents can read
README.md,AGENTS.md, ordocs/DESIGN.md. - Put protocol-critical runtime guidance first in MCP tool descriptions and MCP resources.
- Treat repo docs as human/maintainer guidance unless a client explicitly injects them into model context.
Design Snapshot (Summary Only)
Project direction:
- Use local Claude settings by default (
settingSources: ["user","project","local"]) - Expose only 4 MCP tools (
claude_code,claude_code_reply,claude_code_session,claude_code_check) - Keep startup non-blocking (start/reply return quickly; poll with check)
- Provide three-layer permission control (
advanced.tools+ allow/deny + async decision)
Detailed behavior, full field semantics, and lifecycle mapping:
docs/DESIGN.md#sdk-interface-baselinedocs/DESIGN.md#upgrade-methodologydocs/DESIGN.mdSection 4 (Options mapping matrix)docs/DESIGN.mdSection 5 (SDK message mapping matrix)
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.
- 4d ago First seen · 346 lines · 3,078 tokens per session scan A eea2056543f4
claude-code-mcp AGENTS.md is an instructions file published in the GitHub repository xihuai18/claude-code-mcp (20 stars, last pushed 4mo ago), licensed MIT. It adds 3,078 tokens to every session, about $0.0154 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
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.