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 maintaingit 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/maintain)<a href="https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/maintain"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/maintain/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/maintain"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/maintain.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.00041 | $0.00406 |
| Opus 5.5 | $0.00016 | $0.00162 |
| Sonnet 5.5 | $0.00008 | $0.00081 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
maintain 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
Maintain Skill
Keep the brain knowledge base accurate and current.
When to use
- After a major refactor that changed file structure
- When a command in claude/build.md produces "command not found"
- When claude/architecture.md references a directory that no longer exists
- Periodically as part of session end
Protocol
1. Scan claude/*.md files for staleness signals
Read each claude/*.md file and flag:
- Directory paths that no longer exist
- Commands that fail when run
- Service names that no longer exist in the codebase
{{PLACEHOLDER}}tokens that were never filled in- References to files that have been deleted or moved
2. Verify each flagged item
# Check if a directory exists
ls claude/path/to/check 2>&1
# Check if a command is available
which command_name 2>&1
3. Fix verified stale content
- Update paths to reflect current structure
- Update commands based on current package.json/Makefile
- Remove references to deleted services/modules
- Fill in any remaining
{{PLACEHOLDER}}tokens
4. Add new knowledge (opportunistic)
If you discover new facts about the codebase during maintenance, add them to the appropriate claude/*.md file.
5. Report changes
List every file updated with a one-line description of what changed.
Rules
- NEVER remove knowledge without verifying it's actually stale
- NEVER add speculative content — only add what you've verified
- Document the maintenance run in claude/tasks/lessons.md
- Stale docs are bugs — treat them with the same urgency as code bugs
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 · 52 lines · 41 tokens per session scan A 5052988e115b
maintain is a skill published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 406 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…