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 skills/brain-bootstrap/claude-code-brain-bootstrap/healthnpx skills add brain-bootstrap/claude-code-brain-bootstrap --skill healthgit 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/health)<a href="https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/health"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/health.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.00042 | $0.00864 |
| Opus 5 | $0.00021 | $0.00432 |
| Sonnet 5 | $0.00008 | $0.00173 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
health 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 3d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Health Skill — Claude Brain Configuration Validation
Verify that the Claude Brain configuration is healthy and complete.
Steps
1. CLAUDE.md
- Exists and is not empty
- Line count:
wc -l < CLAUDE.md - Size:
wc -c < CLAUDE.md(budget: ≤32KB = 32768 bytes) - Contains key sections: Skills Roster, Exit Checklist, Terminal Rules
2. settings.json
.claude/settings.jsonexists and is valid JSON:jq . .claude/settings.json- Contains
hooksconfiguration block
3. Hook Scripts
- All
.claude/hooks/*.shfiles exist and are executable:for h in .claude/hooks/*.sh; do test -x "$h" || echo "NOT_EXEC: $h"; done
4. Subagents
- All
.claude/agents/*.mdfiles exist and are non-empty:for f in .claude/agents/*.md; do [ -s "$f" ] || echo "EMPTY: $f"; done
5. Skills
- All
.claude/skills/*/SKILL.mdfiles exist - Each has
name:anddescription:in frontmatter:for f in .claude/skills/*/SKILL.md; do grep -q '^name:' "$f" || echo "BAD FRONTMATTER: $f"; done
6. Error Log
claude/tasks/CLAUDE_ERRORS.mdexists (warn if missing)
7. Secrets Scan
git ls-files | xargs grep -l 'BEGIN.*PRIVATE KEY\|password\s*=\s*[^{][^"\x27]\{8,\}' 2>/dev/null | head -10
Report any matches as ⚠️ warnings.
8. MCP Tool Reachability
Check that the required runtimes are available (all MCP tools run via uvx or npx):
command -v uvx &>/dev/null && echo "uvx: ✅" || echo "uvx: ❌ missing — install via: pip install uv"
command -v npx &>/dev/null && echo "npx: ✅" || echo "npx: ⚠️ missing — install Node.js (for playwright)"
command -v ccc &>/dev/null && echo "cocoindex CLI (ccc): ✅" || echo "cocoindex CLI (ccc): ⚠️ optional — install via: pip install cocoindex"
# uvx-based: codebase-memory-mcp, code-review-graph, serena, cocoindex-code-mcp-server (available when uvx installed)
Report Format
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Claude Brain Health — <repo>
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CLAUDE.md budget ✅ 187 lines / 4.2KB (budget: 32KB)
settings.json ✅ valid JSON + hooks block
Hook scripts ✅ 9/9 executable
Subagents ✅ 5/5 non-empty
Skills ✅ 49/49 have valid frontmatter
Error log ✅ CLAUDE_ERRORS.md exists
Secrets scan ✅ no leaks detected
codebase-memory-mcp ⚠️ missing — run setup-plugins.sh
cocoindex (ccc) ✅ installed
code-review-graph ✅ installed
uvx (playwright/serena) ✅ installed
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Overall: ⚠️ healthy with 1 warning
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
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.
- 3d ago First seen · 82 lines · 42 tokens per session scan A 7609206a77ac
health is a skill published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 864 once invoked, about $0.0002 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-30.
Other skills, from other repositories
implement
TRIGGER when: user asks to implement, fix, build, or work on something — whether from a docs/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-code
Code review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.
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.
design
Use in pre-implementation (idea-to-design) stages to understand spec/requirements and create a correct implementation plan before writing actual code. Turns ideas into a fully-formed PRD/design/specification and implementation-plan. Creates design docs and task lists in docs/wip/.