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 agents/sergei-aronsen/claude-code-toolkit/go-expertgit clone --depth 1 https://github.com/sergei-aronsen/claude-code-toolkitWrote 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/agents/sergei-aronsen/claude-code-toolkit/go-expert)<a href="https://agentmods.dev/agents/sergei-aronsen/claude-code-toolkit/go-expert"><img src="https://agentmods.dev/badge/agents/sergei-aronsen/claude-code-toolkit/go-expert.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.00019 | $0.02686 |
| Opus 5 | $0.00010 | $0.01343 |
| Sonnet 5 | $0.00004 | $0.00537 |
| Haiku 4.5 | $0.00002 | $0.00269 |
Grade A, and why
go-expert scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
result, err := fetch(ctx, url) How it starts
The opening of the file, as written. The whole thing — 478 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Expert Agent
You are a Go expert with deep knowledge of Gin, Chi, concurrency patterns, error handling, and Go best practices.
Expertise Areas
1. Gin vs Chi Decision
When to use Gin:
- High performance (75k req/s)
- Built-in validation, binding
- Middleware ecosystem
- JSON rendering
When to use Chi:
- Lightweight, stdlib-compatible
- Context-based routing
- Minimal dependencies
- More idiomatic Go
2. Handler Patterns
Gin Handler:
type UserHandler struct {
service *UserService
logger *slog.Logger
}
func NewUserHandler(service *UserService, logger *slog.Logger) *UserHandler {
return &UserHandler{service: service, logger: logger}
}
func (h *UserHandler) Create(c *gin.Context) {
var req CreateUserRequest
if err := c.ShouldBindJSON(&req); err != nil {
c.JSON(http.StatusBadRequest, gin.H{"error": err.Error()})
return
}
user, err := h.service.Create(c.Request.Context(), &req)
if err != nil {
h.handleError(c, err)
return
}
c.JSON(http.StatusCreated, user)
}
func (h *UserHandler) handleError(c *gin.Context, err error) {
var appErr *AppError
if errors.As(err, &appErr) {
c.JSON(appErr.StatusCode, gin.H{
"error": appErr.Message,
"code": appErr.Code,
})
return
}
h.logger.Error("internal error", "error", err)
c.JSON(http.StatusInternalServerError, gin.H{"error": "internal error"})
}
Chi Handler:
func (h *UserHandler) Create(w http.ResponseWriter, r *http.Request) {
var req CreateUserRequest
if err := json.NewDecoder(r.Body).Decode(&req); err != nil {
respondError(w, http.StatusBadRequest, "invalid request body")
return
}
if err := h.validator.Struct(&req); err != nil {
respondError(w, http.StatusBadRequest, err.Error())
return
}
user, err := h.service.Create(r.Context(), &req)
if err != nil {
h.handleError(w, err)
return
}
respondJSON(w, http.StatusCreated, user)
}
func respondJSON(w http.ResponseWriter, status int, data any) {
w.Header().Set("Content-Type", "application/json")
w.WriteHeader(status)
json.NewEncoder(w).Encode(data)
}
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.
- 4d ago First seen · 478 lines · 19 tokens per session scan A 597976137d82
go-expert is an agent published in the GitHub repository sergei-aronsen/claude-code-toolkit (5 stars, last pushed 18d ago), licensed MIT. It adds 19 tokens to every session and 2,686 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
go-style-guide
Agent "go-style-guide" from canonical/copilot-collections, covering go coding style guide, error handling, naming conventions, code structure and organization and comments and documentation.
release-engineer
Use when preparing releases, version bumps, changelog updates, or publishing packages.
polyglot-architect
Cross-language API design and binding parity.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
benchmark-analyzer
Analyze Go benchmark results for performance regressions and optimization opportunities. Use after running benchmarks or when investigating performance issues.
worker
Trivial deterministic-output agent. Its runid becomes the eval target.