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.
git clone --depth 1 https://github.com/rlaope/claude-code-savantWrote 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/commands/rlaope/claude-code-savant/savant-node)<a href="https://agentmods.dev/commands/rlaope/claude-code-savant/savant-node"><img src="https://agentmods.dev/badge/commands/rlaope/claude-code-savant/savant-node/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/commands/rlaope/claude-code-savant/savant-node"><img src="https://agentmods.dev/badge/commands/rlaope/claude-code-savant/savant-node.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.00009 | $0.00186 |
| Opus 5.5 | $0.00004 | $0.00074 |
| Sonnet 5.5 | $0.00002 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
savant-node 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
Node.js Optimization - Node.js Developer
$ARGUMENTS
Your Task
Analyze the provided code or question using the Node.js Developer (Node.js Performance Expert) persona.
Execution
Delegate to Node.js Developer agent:
Task tool:
- subagent_type: "claude-code-savant:node-developer"
- prompt: [User's Node.js optimization request]
Response Requirements
Node.js Developer will provide:
- Performance profiling analysis (clinic.js, 0x, autocannon)
- Bottleneck identification at V8/libuv/event loop level
- Before/after code with autocannon benchmark expectations
- Event loop, V8 JIT, Worker threads, and streaming recommendations
- Runtime-specific explanations (why at the V8/event loop internals level)
Return the agent's analysis directly to the user.
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 · 33 lines · 9 tokens per session scan A 757acd7a3e97
savant-node is a command published in the GitHub repository rlaope/claude-code-savant (2 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 186 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
resolve-deps
Diagnose and resolve Swift Package Manager dependency conflicts (launches spm-conflict-resolver agent).
type-coverage
Vérification Couverture des Types Python.
types
Debug and fix TypeScript type errors with systematic analysis and expert guidance.
performance
Diagnose or fix Bun/TypeScript performance. Loads the performance skill, then works the task through its workflow.
axiom-resolve-deps
Diagnose and resolve Swift Package Manager dependency conflicts (Delegate to the spm-conflict-resolver subagent).
build-fix
Fix build and TypeScript errors with minimal changes.