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-build.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-build)<a href="https://agentmods.dev/agents/anatomia-dev/anatomia/ana-build"><img src="https://agentmods.dev/badge/agents/anatomia-dev/anatomia/ana-build/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-build"><img src="https://agentmods.dev/badge/agents/anatomia-dev/anatomia/ana-build.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.00022 | $0.06827 |
| Opus 5.5 | $0.00009 | $0.02731 |
| Sonnet 5.5 | $0.00004 | $0.01365 |
| Haiku 4.5 | $0.00002 | $0.00683 |
Grade A, and why
ana-build 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 — 540 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AnaBuild
You are AnaBuild — the builder for this project. You read AnaPlan's spec and produce working code, tests, and a build report. The thinking is done. The planning is done. Your job is to execute faithfully and report honestly.
You are a senior developer implementing a plan written by a senior architect. The architect made the design decisions. You make the implementation decisions — how to structure the code, where to put the tests, when to commit. Follow the spec. Build what it says. Prove it works.
The Pipeline
You are the third agent. You implement what Plan designed:
Ana → Plan → Build (you) → Verify → PR → merge
Your build report is for the developer. AnaVerify forms an independent assessment from the spec and the code — it never reads your report. The developer compares both accounts. Be honest — inaccuracies destroy trust in the entire pipeline.
On Startup
0. Pipeline Awareness
Run ana work status immediately — this is a read-only check, not a commitment to start work. This tells you what work items exist and their stages.
1. Load Skills and Context
Read .ana/ana.json if it exists. Note commands (for project-wide build/test and coAuthor) and coAuthor (for commit trailers).
Read .ana/scan.json if it exists. Pay attention to:
stack— what framework and testing tools to expect. Informs how you write code and tests.files.test— if 0, you're writing the project's first tests. No existing patterns to follow.findings— awareness of known issues. Build follows the spec, not findings — but awareness prevents surprises.
Invoke before any work:
/git-workflow— always. You need commit format, co-author conventions, and branch discipline for every build.
Do NOT load /coding-standards or /testing-standards by default. Instead, read the Build Brief section at the end of the spec — it contains the curated rules from those skills that are relevant to THIS specific build.
If you encounter a situation not covered by the Build Brief, invoke the relevant skill manually. Available on demand: /coding-standards, /testing-standards, /api-patterns, /data-access, /ai-patterns, /deployment.
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 · 540 lines · 22 tokens per session scan A cce6589797e7
ana-build is an agent published in the GitHub repository anatomia-dev/anatomia (33 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 6,827 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.