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 skills add brain-bootstrap/claude-code-brain-bootstrap --skill plangit clone --depth 1 https://github.com/brain-bootstrap/claude-code-brain-bootstrapWrote 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/skills/brain-bootstrap/claude-code-brain-bootstrap/plan)<a href="https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/plan"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/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/skills/brain-bootstrap/claude-code-brain-bootstrap/plan"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/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.00042 | $0.00513 |
| Opus 5.5 | $0.00017 | $0.00205 |
| Sonnet 5.5 | $0.00008 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
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.
What it actually says
Plan Skill
Create a structured, checkable implementation plan before writing any code.
When to use
- Task requires 3 or more steps
- Task touches multiple files or layers
- Task involves an architectural decision
- Any time the path forward is not immediately obvious
Protocol
1. Read mandatory context first
claude/tasks/todo.md— current task state (are we resuming?)claude/tasks/lessons.md— relevant past lessonsclaude/architecture.md— project structureclaude/rules.md— golden rules
2. Understand the full scope
- What is the exact goal? What does done look like?
- What layers does this touch (schema, service, API, tests, docs)?
- What already exists that is relevant?
- What are the failure modes?
3. Write the plan to claude/tasks/todo.md
Format:
# Task: <Clear, concise title>
**Goal:** <One sentence. What is done when this is complete?>
**Branch:** <git branch name, if applicable>
**Loaded docs:** <which claude/*.md files you read>
## Steps
- [ ] 1. <First action — specific file or command>
- [ ] 2. <Second action>
- [ ] 3. <Third action>
...
## Review Checklist
- [ ] Tests pass
- [ ] Linter passes
- [ ] No new warnings
- [ ] PR description ready (if applicable)
## Notes
<Any constraints, risks, or decisions to track>
4. Validate the plan (optional — for complex tasks)
Spawn a plan-challenger subagent:
"Spawn plan-challenger to review this plan. Here is the plan: [paste plan]"
5. Get approval for non-trivial plans
Present the plan to the user. Wait for "proceed" or revisions before implementing.
Rules
- NEVER start implementing before the plan is written
- NEVER mark a step complete without proof (test result, output, etc.)
- If something goes wrong mid-execution: STOP, re-read the plan, update it, then continue
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 · 67 lines · 42 tokens per session scan A 00f4ed698e7d
plan is a skill published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 513 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
implement
TRIGGER when: user asks to implement, fix, build, or work on something — whether from a docs/feat/wip plan OR a standalone task (bug fix, GitHub issue, one-off change). Examples: "work on task 1", "fix this bug", "implement feature X from the issue". Provides structured execution with profile detection, dependency…
review-spec
Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.
chain-of-verification
Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.
review-design
Review design, implementation, and task documents produced by design. Evaluates document quality, internal consistency, and technical soundness. Use after design completes and before starting implement.
review-architecture
Review a written architecture artifact — an ADR (docs/adr/), a broader architecture doc, the architecture section of a design doc, or a domain-reference kit (glossary + traps pages, reviewed as one composite artifact) — against the system it claims to describe. Verifies the EXISTENCE and TOPOLOGY of declared…
model
Produce or update a domain-reference kit — the durable glossary + divergences/traps pages for a bounded context. Use for domain modelling, information architecture, building a domain glossary or domain model, mapping domain concepts to code (bindings), or surfacing the decidable questions stakeholders must close…