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/madeye/mcp-cli/claude-mdgit clone --depth 1 https://github.com/madeye/mcp-cliWhat 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.01978 | $0.01978 |
| Opus 5 | $0.00989 | $0.00989 |
| Sonnet 5 | $0.00396 | $0.00396 |
| Haiku 4.5 | $0.00198 | $0.00198 |
Grade A, and why
mcp-cli 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 2d 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 — 99 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.
Commands
CI gates (must pass before pushing — see user global rules):
cargo fmt --all -- --check
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace --all-targets
Other common commands:
cargo build --release # build both binaries
cargo run -p daemon -- --root /path/to/project # run daemon (default socket: /tmp/mcp-cli.sock)
cargo run -p mcp-bridge # run stdio bridge
cargo test -p daemon changelog::tests::push_advances_version # single test by path
cargo test -p daemon -- --nocapture # see tracing output from tests
RUST_LOG=debug cargo run -p daemon # bump log level (daemon defaults to info, bridge to warn)
Daemon flags worth knowing: --socket, --root, --changelog-capacity (ring size, default 4096), --search-cache-capacity (LRU size, default 64; 0 disables), --parse-cache-capacity (tree-sitter parse LRU, default 256; 0 disables), --no-prewarm (skip startup page-cache walk — useful in tests/benchmarks).
Architecture
Three-crate Cargo workspace implementing a sidecar daemon + thin MCP bridge pattern. The point is to amortize kernel overhead: agents make hundreds of small fs.read / git.status / search.grep calls, and each one hits a long-lived in-process daemon instead of forking cat/git/rg.
MCP client (Claude Code / Codex) ──stdio──> mcp-cli-bridge ──UDS──> mcp-cli-daemon
(crates/mcp-bridge) (crates/daemon)
↑ owns project state:
mmap, libgit2, grep-searcher,
notify-rs watcher + ChangeLog
Crates
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.
- 2d ago First seen · 99 lines · 1,978 tokens per session scan A 0507ab079d76
mcp-cli CLAUDE.md is an instructions file published in the GitHub repository madeye/mcp-cli (117 stars, last pushed 4mo ago), licensed MIT. It adds 1,978 tokens to every session, about $0.0099 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
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.
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).
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.