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-go)<a href="https://agentmods.dev/commands/rlaope/claude-code-savant/savant-go"><img src="https://agentmods.dev/badge/commands/rlaope/claude-code-savant/savant-go.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.1 | $0.00007 | $0.00168 |
| Opus 5 | $0.00003 | $0.00084 |
| Sonnet 5 | $0.00001 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
savant-go 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 7d 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
Go Optimization - Go Developer
$ARGUMENTS
Your Task
Analyze the provided code or question using the Go Developer (Go Performance Expert) persona.
Execution
Delegate to Go Developer agent:
Task tool:
- subagent_type: "claude-code-savant:go-developer"
- prompt: [User's Go optimization request]
Response Requirements
Go Developer will provide:
- Performance profiling analysis (pprof CPU, heap, goroutine)
- Bottleneck identification at Go runtime level
- Before/after code with go test -bench expectations
- Goroutine, GC, escape analysis, and concurrency recommendations
- Runtime-specific explanations (why at the Go runtime 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.
- 7d ago First seen · 33 lines · 7 tokens per session scan A 7950f149199e
savant-go is a command published in the GitHub repository rlaope/claude-code-savant (2 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 168 once invoked, about $0.0000 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-31.
Other commands, from other repositories
go-build
Fix Go build errors, go vet warnings, and linter issues incrementally. Invokes the go-build-resolver agent for minimal, surgical fixes.
go-build
A command for diagnosing and fixing Go build errors, vet warnings, and linter problems in small, incremental changes. Go is a programming language, and these tools check whether Go code builds and follows common rules.
go-build
Fix Go build errors, go vet warnings, and linter issues incrementally. Invokes the go-build-resolver agent for minimal, surgical fixes.
go-build
Fix Go build and vet errors.
lint-fix
Run golangci-lint tool and fix all reported issues.
go-build
Fix Go build and vet errors.