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/gusdawn123/cpp-analysis-mcp/claude-mdgit clone --depth 1 https://github.com/GusDawn123/cpp-analysis-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/gusdawn123/cpp-analysis-mcp/claude-md)<a href="https://agentmods.dev/instructions/gusdawn123/cpp-analysis-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/gusdawn123/cpp-analysis-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 | $0.01599 | $0.01599 |
| Opus 5 | $0.00800 | $0.00800 |
| Sonnet 5 | $0.00320 | $0.00320 |
| Haiku 4.5 | $0.00160 | $0.00160 |
Grade A, and why
cpp-analysis-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 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — how this repo is worked
Instructions for Claude (any machine, any session). These encode the maintainer's standing decisions; they override default behavior. When they conflict with something newer the maintainer says, the maintainer wins — then update this file.
Read first, always
docs/getting-started.md— the contributing workflow lives at the bottom. It was missed once; it is never missed again.git branch -rbefore assuming anything about branches. This repo had in-flight feature branches a session once ignored.docs/architecture.md(v1 layers, four rules) anddocs/architecture-v2.md(five-layer target: surface / planner / analyzers / store / engines).- ADRs in
docs/adr/are binding decisions, each with its precedents.
Source control (non-negotiable)
- git-flow:
feat/...branches fork fromdevelop, PRs targetdevelop, green CI required.mainonly receives merges fromdevelopat release. - Never merge a PR. The maintainer merges, or delegates explicitly per-PR.
- One branch per chunk, one conventional commit per sub-chunk.
- Commit/PR titles:
type(scope): imperative summary(feat, fix, docs, refactor, chore, test). Never internal plan vocabulary ("Phase 1", "Chunk 1.2") in titles — plan words live in specs and milestones, not git history.
The working ritual (per sub-chunk, six steps, no skipping)
- Plan — goal, files touched, interface changes, test plan, performance notes (data structures with complexity stated), risks and judgment calls.
- Refine — the maintainer tears it up; nothing is written before their blessing.
- Implement — tests first, code second, in the repo's voice (see "Comments &
docs" below; comments say why; match what surrounds you).
- 3.5 Self-review — a deliberate pass for simplicity, naming, dead weight, idiom-match, before any external review.
- Review — CodeRabbit CLI on exactly that diff (
coderabbit review --agent -t uncommitted). Code diffs only — never run it on docs-only changes. - Fix — verify every finding against the code before acting; accept what is real, reject with a recorded reason (docstring, test, or commit message) what is not. Findings are data, not orders.
- Commit — one conventional commit whose message tells the story, including design corrections and rejected-finding reasons.
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 · 122 lines · 1,599 tokens per session scan A f78521a8db39
cpp-analysis-mcp CLAUDE.md is an instructions file published in the GitHub repository GusDawn123/cpp-analysis-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 1,599 tokens to every session, about $0.0080 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-31.
Other instructions, from other repositories
blockrun-mcp AGENTS.md
AGENTS.md instructions for BlockRunAI/blockrun-mcp, covering blockrun mcp, commands, project structure, key dependencies and install in codex.
openrouter-mcp-multimodal AGENTS.md
Instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
intervals-icu-mcp CLAUDE.md
Instructions for hhopke/intervals-icu-mcp, covering claude.md, project overview, development commands, architecture (quick reference) and tool categories.
ai-toolkit AGENTS.md
Instructions for pipefy/ai-toolkit, covering repository guidelines, documentation map, project structure, import namespace migration: pipefysdk → pipefy and src/pipefysdk/init.py (transitional shim).
flyto-core CLAUDE.md
Instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.
Plonk AGENTS.md
Instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.