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 sergei-aronsen/claude-code-toolkit --skill gogit 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/skills/sergei-aronsen/claude-code-toolkit/go)<a href="https://agentmods.dev/skills/sergei-aronsen/claude-code-toolkit/go"><img src="https://agentmods.dev/badge/skills/sergei-aronsen/claude-code-toolkit/go/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/sergei-aronsen/claude-code-toolkit/go"><img src="https://agentmods.dev/badge/skills/sergei-aronsen/claude-code-toolkit/go.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.00019 | $0.02414 |
| Opus 5.5 | $0.00008 | $0.00966 |
| Sonnet 5.5 | $0.00004 | $0.00483 |
| Haiku 4.5 | $0.00002 | $0.00241 |
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 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.
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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Expert Skill
This skill provides deep Go expertise including Gin/Chi patterns, goroutines, error handling, table-driven tests, and security best practices.
Error Handling
Always Check Errors
// ✅ Correct - check and wrap
user, err := repo.GetByID(ctx, id)
if err != nil {
return nil, fmt.Errorf("failed to get user %s: %w", id, err)
}
// ❌ Wrong - ignoring error
user, _ := repo.GetByID(ctx, id) // Never do this!
Custom Error Types
type AppError struct {
StatusCode int `json:"-"`
Code string `json:"code"`
Message string `json:"message"`
Err error `json:"-"`
}
func (e *AppError) Error() string {
if e.Err != nil {
return fmt.Sprintf("%s: %v", e.Message, e.Err)
}
return e.Message
}
func (e *AppError) Unwrap() error {
return e.Err
}
// Constructors
func ErrNotFound(resource string) *AppError {
return &AppError{
StatusCode: http.StatusNotFound,
Code: "NOT_FOUND",
Message: fmt.Sprintf("%s not found", resource),
}
}
func ErrBadRequest(message string) *AppError {
return &AppError{
StatusCode: http.StatusBadRequest,
Code: "BAD_REQUEST",
Message: message,
}
}
Error Checking
// Check specific error types
func handleError(err error) {
var appErr *AppError
if errors.As(err, &appErr) {
// Handle app error
log.Printf("App error: %s", appErr.Code)
return
}
if errors.Is(err, context.DeadlineExceeded) {
// Handle timeout
log.Println("Request timed out")
return
}
if errors.Is(err, sql.ErrNoRows) {
// Handle not found
return
}
// Unknown error
log.Printf("Unexpected error: %v", err)
}
Concurrency Patterns
Worker Pool
func ProcessItems(ctx context.Context, items []Item, workers int) error {
jobs := make(chan Item, len(items))
results := make(chan error, len(items))
// Start workers
var wg sync.WaitGroup
for i := 0; i < workers; i++ {
wg.Add(1)
go func() {
defer wg.Done()
for item := range jobs {
select {
case <-ctx.Done():
results <- ctx.Err()
return
default:
results <- processItem(ctx, item)
}
}
}()
}
// Send jobs
for _, item := range items {
jobs <- item
}
close(jobs)
// Wait and close results
go func() {
wg.Wait()
close(results)
}()
// Collect errors
var errs []error
for err := range results {
if err != nil {
errs = append(errs, err)
}
}
return errors.Join(errs...)
}
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 · 439 lines · 19 tokens per session scan A fae906bb022a
Go Expert is a skill published in the GitHub repository sergei-aronsen/claude-code-toolkit (5 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 2,414 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
golang-patterns
Go-specific design patterns and best practices including functional options, small interfaces, dependency injection, concurrency patterns, error handling, and package organization. Use when working with Go code to apply idiomatic Go patterns.
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-samber-oops
Structured error handling in Golang with samber/oops — error builders, stack traces, error codes, error context, error wrapping, error attributes, user-facing vs developer messages, panic recovery, and logger integration. Apply when using or adopting samber/oops, or when the codebase already imports…
golang-uber-fx
Golang application framework using uber-go/fx — fx.New, fx.Provide, fx.Invoke, fx.Module, fx.Lifecycle hooks, fx.Annotate (name/group/As), fx.Decorate, fx.Supply, fx.Replace, fx.WithLogger, and signal-aware Run(). Apply when using or adopting uber-go/fx, when the codebase imports go.uber.org/fx, or when wiring…
ax-go-agent-optimize
Use when writing Go code with github.com/ax-llm/ax/packages/go for agent optimization, verified agent-playbook evolution, evaluators, judges, optimizer artifacts, BootstrapFewShot, and GEPA.