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/sdsrss/claudemd/claude-mdgit clone --depth 1 https://github.com/sdsrss/claudemdWrote 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/sdsrss/claudemd/claude-md)<a href="https://agentmods.dev/instructions/sdsrss/claudemd/claude-md"><img src="https://agentmods.dev/badge/instructions/sdsrss/claudemd/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.00691 | $0.00691 |
| Opus 5 | $0.00345 | $0.00345 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
claudemd 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 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AUTONOMY_LEVEL: aggressive
Solo OSS maintainer running with bypassPermissions. Atomic-ship convention applies (commit + push + tag + push tag + gh release create in one turn) — see feedback_claudemd_ship_from_main_atomic.md. §5.1 Never-downgrade set binds as written in core §5.1 (single source; the verbatim list was deduped here 2026-07-25 — it drifts).
Code Graph (repo-wide AST index)
AST + FTS + vector index of the whole repo — prefer over multi-round Grep/Read for structural queries (LSP only sees open files; this sees everything). Fastest path = Bash CLI:
| Intent | Command |
|---|---|
| Who calls X / what X calls | code-graph-mcp callgraph X |
| Impact before editing a fn | code-graph-mcp impact X |
| Unfamiliar dir / module | code-graph-mcp overview <dir> |
| Symbol source / signature | code-graph-mcp show X |
| Concept search (no exact name) | code-graph-mcp search "…" (vector: MCP semantic_code_search) |
| grep + AST context | code-graph-mcp grep "pat" [paths] [-t lang] [-g glob] [-c] |
Still use Grep for literal strings/regex in non-code files; still Read files you'll edit.
Full command + MCP-tool table: .claude/plugin_code_graph_mcp.md
claude-mem-lite — persistent memory
PreToolUse hooks already run mem_recall for past lessons before Read/Edit/Write. The calls worth making proactively:
| When | Call |
|---|---|
| Before Edit/Write | hook already recalled; if a #NN lesson was injected, cite #NN next time you produce user-visible text (citing = adopting the feedback; uncited lessons decay) |
| After fixing a non-trivial bug | mem_save(type="bugfix", lesson_learned="<root cause + fix>", importance=2) |
| After a non-obvious architecture decision | mem_save(type="decision", lesson_learned="<constraint + tradeoff>") |
| Deferring to a future session | `mem_defer({title, priority:1 |
| Looking up past work / history | mem_search "keywords" · mem_recent · mem_timeline |
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 · 41 lines · 691 tokens per session scan A 4fe3d1bea3b8
claudemd CLAUDE.md is an instructions file published in the GitHub repository sdsrss/claudemd (2 stars, last pushed 11d ago), licensed MIT. It adds 691 tokens to every session, about $0.0035 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
handoff CLAUDE.md
Instructions for AbdurRafay2004/handoff, covering claude.md, what this repo is, runtime model (how the pieces connect), invariants — do not break these when editing hooks and working / testing the hooks.
CTX CLAUDE.md
Instructions for pluto2060/CTX, covering 새 ctx 정의 — 실제 production 구성 (settings.json 기준), 현재 wired hooks (production), 은퇴한 / 아카이브 hooks (wired 아님, 실행 안 됨), 공유 인프라 and g1/g2 정의 (2026-04-03 명료화).
brooks-lint AGENTS.md
AGENTS.md instructions for hyhmrright/brooks-lint, covering agents.md, core purpose, skill integration, engineering standards and project structure.
vibeguard AGENTS.md
AGENTS.md instructions for majiayu000/vibeguard, covering agent instructions, scope, start here, core rules and delivery policy.
logic-lens GEMINI.md
Instructions for hyhmrright/logic-lens, covering logic-lens — developer guide (gemini cli), invoking skills, installation, project layout and key conventions.
evolve-loop GEMINI.md
Gemini CLI instructions for mickeyyaya/evolve-loop, covering project instructions (gemini cli), skill discovery, runtime adapter (tier-1-hybrid), tool name translation and invariants (apply to gemini context too).