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/rasatpetabit/masterplan/claude-mdgit clone --depth 1 https://github.com/rasatpetabit/masterplanWrote 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/rasatpetabit/masterplan/claude-md)<a href="https://agentmods.dev/instructions/rasatpetabit/masterplan/claude-md"><img src="https://agentmods.dev/badge/instructions/rasatpetabit/masterplan/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.00272 | $0.00272 |
| Opus 5 | $0.00136 | $0.00136 |
| Sonnet 5 | $0.00054 | $0.00054 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
masterplan 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.
What it actually says
CLAUDE.md — masterplan
Thin Claude Code shim. Canonical repo instructions are imported below; do not add vendor-neutral policy here — put it in AGENTS.md.
@AGENTS.md
Central cross-repo policy (AUQ, Serena, Hindsight, context-mode, model
routing) resolves from the repo-local policy/workflow-map.json (a checked-in
copy of the fleet workflow routing map) and the fleet dispatch policy at
/srv/workflows/policy/dispatch.md. Never copy that policy here.
Claude Code specifics
- All user-facing questions go through
AskUserQuestion; never end a turn with prose questions. - Use Claude Code plugins, hooks, plan mode, and slash commands only as documented by repo-local
AGENTS.mdor active plugin settings.
- This repo IS the Claude Code plugin:
/masterplanroutes throughcommands/masterplan.md; manifests live in.claude-plugin/. AGENTS.md (imported above) is a thin index — the five-layer architecture lives indocs/internals.md, and build/test + contributor discipline indocs/development.md.
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 · 22 lines · 272 tokens per session scan A c1682a23a85c
masterplan CLAUDE.md is an instructions file published in the GitHub repository rasatpetabit/masterplan (9 stars, last pushed 4d ago), licensed MIT. It adds 272 tokens to every session, about $0.0014 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
river-review GEMINI.md
Gemini CLI instructions for s977043/river-review, covering gemini instructions (river-review), 必須チェック, gemini-specific tips, prompt assembly and development tips.
living-manual CLAUDE.md
Instructions for dougstanford/living-manual, covering living-manual, start of every session, how work lands — non-negotiable, user's manual (living-manual) and releasing.
ship-it open-pr.instructions.md
Instructions for khrichtchatyi/ship-it: When the user asks to open, create, or submit a pull request, follow the skill in skills/open-pr/SKILL.md in full: verify gh is authenticated, resolve the target repository and default branch, push the current branch, open one pull request with a title and body derived from the…
agent-skills CLAUDE.md
Instructions for mindbox-cloud/agent-skills, covering agent-skills — developer guide for claude code, repository purpose, repository structure, how to add a new plugin and step 1 — create the directory structure.
my-claude-skills CLAUDE.md
Instructions for brody-0125/my-claude-skills, covering claude code skills repository, validation commands, sub-kopring-engineer: kotlin/java 코드 컨벤션 검증, numerical: 수치 연산 코드 검증 and sub-test-engineer: 문서 일관성 검증.
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).