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 mcpgit 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/mcp)<a href="https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/mcp"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/mcp/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/mcp"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/mcp.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.00035 | $0.00850 |
| Opus 5.5 | $0.00014 | $0.00340 |
| Sonnet 5.5 | $0.00007 | $0.00170 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
mcp 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Skill
Manage Model Context Protocol (MCP) servers for this project.
Usage
/mcp # List configured servers + invocation format
/mcp status # Check which tool binaries are installed
/mcp add <server> # Add a new MCP server
/mcp format # Show all tool invocation strings
MCP Tool Invocation Format
mcp__SERVER_KEY__TOOL_FUNCTION_NAME
Where SERVER_KEY is the server key in .claude/settings.json under mcpServers.*.
Instructions
If list or empty:
- Read
.claude/settings.json— show currently configuredmcpServersentries - Show invocation format for each tool
- Suggest additional servers based on tech stack in
claude/architecture.md
If status:
- Check which MCP binaries are installed:
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" command -v ccc &>/dev/null && echo "cocoindex CLI (ccc): ✅" || echo "cocoindex CLI: ⚠️ optional — install via: pip install cocoindex" # uvx-based tools (codebase-memory, code-review-graph, serena, cocoindex-code) are available when uvx is installed
If add <server-name>:
- Prefer CLI:
claude mcp add <server-name> -- <command> [args]- Example:
claude mcp add context7 -- npx -y @upstash/context7-mcp
- Example:
- Or manually add to
.claude/settings.jsonundermcpServers.<name> - For HTTP servers requiring OAuth: authenticate after configuration
- Update
CLAUDE.md— add to Plugin Ecosystem section
If format:
Show all available MCP tool invocations from .claude/settings.json.
Pre-Configured MCP Stack
| MCP Server Key | Binary | Invocation prefix |
|---|---|---|
codebase-memory |
uvx codebase-memory-mcp@latest |
mcp__codebase-memory__ |
cocoindex-code |
uvx cocoindex-code-mcp-server@latest |
mcp__cocoindex-code__ |
code-review-graph |
uvx code-review-graph@latest |
mcp__code-review-graph__ |
serena |
uvx serena@latest |
mcp__serena__ |
playwright |
npx @playwright/mcp@latest |
mcp__playwright__ |
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 · 86 lines · 35 tokens per session scan A 1a1ea2c4362e
mcp is a skill published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 850 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-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…