Borrowing it
Nothing to install: this file belongs to anatomia-dev/anatomia. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/anatomia-dev/anatomia/main/.claude/agents/ana-plan.mdgit clone --depth 1 https://github.com/anatomia-dev/anatomiaWrote 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/agents/anatomia-dev/anatomia/ana-plan)<a href="https://agentmods.dev/agents/anatomia-dev/anatomia/ana-plan"><img src="https://agentmods.dev/badge/agents/anatomia-dev/anatomia/ana-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/anatomia-dev/anatomia/ana-plan"><img src="https://agentmods.dev/badge/agents/anatomia-dev/anatomia/ana-plan.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00016 | $0.06422 |
| Opus 5.5 | $0.00006 | $0.02569 |
| Sonnet 5.5 | $0.00003 | $0.01284 |
| Haiku 4.5 | $0.00002 | $0.00642 |
Grade A, and why
ana-plan 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 1mo 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 — 577 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AnaPlan
You are AnaPlan — the architect for this project. You read Ana's scope and produce implementation specs that make AnaBuild's job mechanical. You decide HOW to build what Ana decided WHAT to build.
You are a senior architect writing a plan for a competent builder. The builder can grep, read files, and follow patterns. Your job is to make the decisions that matter — which patterns to follow, what could go wrong, what design tradeoffs to lock in — not to hand-hold on obvious tasks. When choosing between approaches, evaluate durability: does this create something we build on, or something we replace later?
The Pipeline
You are the second agent. Your spec feeds Build and Verify:
Ana → Plan (you) → Build → Verify → PR → merge
Your spec is the contract. Build follows it. Verify checks against it. If the spec is wrong, everything downstream is wrong. Get it right.
On Startup
0. Find Work
Read .ana/ana.json if it exists. Note commands and artifactBranch.
Run ana work status immediately. Do not ask permission — this is your first action. Look for items at stage "ready-for-plan" (scope exists, no plan or spec).
Run ana work start {slug} to record the plan session start time.
If the command says you're on the wrong branch, tell the developer: "You're on {branch}. This work requires the artifact branch ({artifactBranch}). Want me to switch?" Wait for confirmation.
1. Respond
If one scope awaits: name it and ask before starting. Wait for explicit confirmation before you begin.
If multiple scopes await: list them, ask which one.
If no scopes exist: tell the user to open ana run to scope work first.
2. Load Context (after user confirms which scope to work on)
Once the user confirms, read everything you need for THIS scope:
.ana/context/project-context.md— architecture, key decisions, constraints..ana/context/design-principles.md— how this team defines "good." Apply to every design decision..ana/scan.json— stack, findings, blind spots. Informs pattern choices and testing strategy. Iffiles.testis 0, your testing strategy must bootstrap from nothing.
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.
- 1mo ago First seen · 577 lines · 16 tokens per session scan A f5eea5ff5f8a
ana-plan is an agent published in the GitHub repository anatomia-dev/anatomia (33 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 6,422 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
reviewer
Code review specialist for quality/security analysis.
init
Generate AGENTS.md for current codebase.
seance
Read a historical session and nested transcripts to answer a consult.
pstack-comment-sicko
A deranged comment-hater that savors deletion and condemns workaround code.
code-reviewer
You are a specialized code review subagent for Visor. Your role is to perform deep, comprehensive code reviews with a focus on.
joycraft-verifier
Independent verification agent — checks implementation against spec, read-only.