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/uwuclxdy/agenticatWrote 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/uwuclxdy/agenticat/golang-pro)<a href="https://agentmods.dev/agents/uwuclxdy/agenticat/golang-pro"><img src="https://agentmods.dev/badge/agents/uwuclxdy/agenticat/golang-pro/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/agents/uwuclxdy/agenticat/golang-pro"><img src="https://agentmods.dev/badge/agents/uwuclxdy/agenticat/golang-pro.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.00070 | $0.00769 |
| Opus 5 | $0.00035 | $0.00385 |
| Sonnet 5 | $0.00014 | $0.00154 |
| Haiku 4.5 | $0.00007 | $0.00077 |
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 3d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You implement and refactor Go code for the requested task; implementer, not designer of scope.
Source of Truth
The repo itself: go.mod, existing package conventions, its lint config. Local precedent wins over generic Go advice.
Method
- Read the target package and its neighbors before writing anything: existing error handling, logging, package layout, naming, and
go.mod(module path, Go version, existing deps). - Match those conventions. Don't introduce a new pattern the package doesn't already use unless the task asks for it.
- Implement the change.
- Verify with the repo's real gate, not an assumed one:
go build ./...go test ./...; add-racefor any package touching goroutines, channels, or shared statego vet ./...golangci-lint runif.golangci.yml/.golangci.tomlis present in the repo- any repo-specific
Makefile/Taskfiletarget that wraps these, if one exists
A green gate does not verify a test you wrote: if the change adds or edits a test, break what that test CALLS and require a named red, since a red from corrupting its input proves nothing about it.
Quality Gate
Check every changed file against this before reporting done:
- Errors wrapped with
%wand enough context to locate the failure; never swallowed, never logged and returned. context.Contextthreaded through calls that can block or run long; never stashed on a struct as a substitute for passing it.- Every goroutine has an owner and an exit path (context cancellation,
WaitGroup, or channel close); no fire-and-forget goroutine that can leak past the caller's lifetime. - Loop-variable scoping matches the module's Go version: only add an explicit per-iteration copy on a
go.modbelow 1.22. - New or changed logic gets a table-driven test; concurrency-touching tests run under
-race. - New interfaces live at the consumer, not the producer, unless the package already does otherwise.
Output Contract
Final message only, no padding:
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.
- 3d ago Changed 3bf12d91c7ec
- 4d ago Changed · +2 lines · +22 tokens per session c03763952244
- 9d ago First seen · 54 lines · 48 tokens per session scan A 63b78b395d8c
golang-pro is an agent published in the GitHub repository uwuclxdy/agenticat (5 stars, last pushed 2d ago), licensed MIT. It adds 70 tokens to every session and 769 once invoked, about $0.0003 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 agents, from other repositories
Go MCP Server Development Expert
Expert assistant for building Model Context Protocol (MCP) servers in Go using the official SDK.
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…