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 serenagit 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/serena)<a href="https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/serena"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/serena/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/serena"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/serena.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.00037 | $0.00836 |
| Opus 5.5 | $0.00015 | $0.00334 |
| Sonnet 5.5 | $0.00007 | $0.00167 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
serena 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Serena — LSP-Backed Symbol Refactoring
MCP server key: serena — tools: mcp__serena__*
Core principle: Type-aware, 100% recall. Grep finds strings; Serena finds symbols — including aliased imports, dynamic usages, and type-renamed references.
Decision Matrix
| Question | Use |
|---|---|
"Rename AuthService everywhere" |
serena — rename_symbol |
"Find all callers of login()" |
serena — find_references |
"Move UserMapper to another file" |
serena — move_symbol |
"Inline the MAX_RETRIES constant" |
serena — inline_symbol |
| "Find code about rate limiting" | cocoindex-code — semantic meaning |
| "Who calls AuthService in the graph?" | codebase-memory-mcp — architecture overview |
| "Is renaming this safe to ship?" | code-review-graph — blast radius |
Key Tools
mcp__serena__find_symbol(name, type?) — find by name/type (LSP, not grep)
mcp__serena__find_references(symbol) — all usages across the project
mcp__serena__get_symbol_info(symbol) — signature, docstring, defined-in, refs
mcp__serena__rename_symbol(symbol, new_name) — rename everywhere atomically
mcp__serena__move_symbol(symbol, target_file) — move + fix all imports
mcp__serena__replace_symbol_body(symbol, body) — replace impl, keep signature
mcp__serena__inline_symbol(symbol) — inline at all call sites
mcp__serena__get_call_graph(symbol) — call graph from a symbol
Standard Workflows
Rename across codebase:
1. mcp__serena__find_symbol("OldName") → confirm it's the right symbol
2. mcp__serena__find_references("OldName") → verify scope
3. mcp__serena__rename_symbol("OldName", "NewName") → atomic rename
Move a class to another file:
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 · 85 lines · 37 tokens per session scan A a6433da50bc8
serena is a skill published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 836 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…