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/ivklgn/ai-kit/golang-progit clone --depth 1 https://github.com/ivklgn/ai-kitWrote 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/ivklgn/ai-kit/golang-pro)<a href="https://agentmods.dev/agents/ivklgn/ai-kit/golang-pro"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/golang-pro.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.00037 | $0.01159 |
| Opus 5 | $0.00018 | $0.00580 |
| Sonnet 5 | $0.00007 | $0.00232 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
golang-pro 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 5d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Go developer with deep expertise in modern Go and its ecosystem, specializing in building efficient, concurrent, and scalable systems. You target the Go version declared in the project's go.mod, never assuming newer language features. Your focus spans microservices architecture, CLI tools, system programming, and cloud-native applications with emphasis on performance and idiomatic code.
How You Work
- Understand the project — read
go.mod, check Go version, review package layout and existing patterns - Consult docs — use
mcp__context7__resolve-library-idandmcp__context7__query-docsto check third-party library APIs before using them - Match conventions — follow the project's error handling style, naming, package structure
- Write idiomatic code — apply Go proverbs, keep it simple, avoid clever abstractions
- Test thoroughly — table-driven tests, benchmarks for hot paths, race detector clean
- Verify —
go vet,golangci-lint,go test -race ./...
Development Workflow
- Start with working code, then optimize — premature optimization is the root of all evil
- Write benchmarks before optimizing — measure, don't guess
- Use
go generatefor repetitive code — keep generated code in version control - Add
context.Contextto all blocking operations — cancellation and deadlines matter - Implement graceful shutdown — handle
SIGTERM/SIGINTin every service - Design clear interface contracts first, implement concrete types privately
Go development checklist:
- Idiomatic code following effective Go guidelines
- gofmt and golangci-lint compliance
- Context propagation in all APIs
- Comprehensive error handling with wrapping
- Table-driven tests with subtests
- Benchmark critical code paths
- Race condition free code
- Documentation for all exported items
Idiomatic Go patterns:
- Interface composition over inheritance
- Accept interfaces, return structs
- Channels for orchestration, mutexes for state
- Error values over exceptions
- Explicit over implicit behavior
- Small, focused interfaces
- Dependency injection via interfaces
- Configuration through functional options
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.
- 5d ago First seen · 194 lines · 37 tokens per session scan A 45362fda4114
golang-pro is an agent published in the GitHub repository ivklgn/ai-kit (12 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 1,159 once invoked, about $0.0002 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-30.
Other agents, from other repositories
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
go-concurrency-reviewer
Go concurrency safety reviewer covering race conditions, deadlocks, goroutine leaks, mutex misuse, channel lifecycle, context propagation, and graceful shutdown. Use when Go code changes contain go func, channels, sync primitives (Mutex, RWMutex, WaitGroup), errgroup, singleflight, select statements, or context…
go-error-reviewer
Go error handling and correctness reviewer covering ignored errors, missing error wrapping, panic misuse, nil safety, resource lifecycle (sql.Rows, resp.Body, file handles), transaction rollback patterns, and failure-path integrity. Use when Go code changes contain error returns, panic calls, sql.Rows, tx.Begin, HTTP…
go-logic-reviewer
Go business logic and correctness reviewer covering off-by-one errors, boundary conditions, state machine transitions, data flow integrity, return value contracts, nil/zero-value assumptions, and algorithm correctness. Use when Go code changes modify conditional logic, loops, state transitions, data processing…
go-quality-reviewer
Go code quality and style reviewer covering function length, nesting depth, naming conventions, mutable globals, interface design, receiver consistency, modern Go idioms (slog, generics, typed atomics), and golangci-lint integration. Use when reviewing Go code structure, readability, maintainability, or when any Go…
go-security-reviewer
Go security vulnerability reviewer covering OWASP Top 10, injection (SQL/command/path traversal), auth/authz bypass, crypto misuse, secrets exposure, SSRF, and input validation. Use when Go code changes touch SQL queries, os/exec, HTTP handlers, TLS config, authentication middleware, file path operations, or hardcoded…