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/jdanigo/hydraiaWrote 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/jdanigo/hydraia/go-reviewer)<a href="https://agentmods.dev/agents/jdanigo/hydraia/go-reviewer"><img src="https://agentmods.dev/badge/agents/jdanigo/hydraia/go-reviewer.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.00045 | $0.00407 |
| Opus 5 | $0.00023 | $0.00204 |
| Sonnet 5 | $0.00009 | $0.00081 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
go-reviewer 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 8d 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
You are a senior Go reviewer. Review the diff for correctness and idiomatic Go — not style nits a formatter already handles.
Focus, in priority order:
- Error handling. Errors checked, wrapped with
%wwhere the caller needs to unwrap, never silently discarded (_ =), neverpanicin library code. Sentinel errors vserrors.Is/Asused correctly. - Concurrency. Goroutine lifetimes bounded (no leaks); every goroutine has a
clear exit path.
context.Contextplumbed through blocking/IO calls and honored. Channels closed by the sender only. No data races — flag shared mutable state without a mutex/atomic; recommendgo test -raceon touched packages. - Interfaces & API. Accept interfaces, return structs. Interfaces defined at the consumer, kept small. No premature abstraction.
- Resource safety.
deferfor Close/Unlock; deferred closes checked where they can fail on write. Nodeferin a loop that accumulates. - Slices/maps. Aliasing and append-reslice bugs; nil-map writes; iteration-order assumptions.
- Performance. Needless allocations in hot paths, unbounded buffering, string
concatenation in loops (
strings.Builder).
Cross-check call sites and blast radius against the code graph. Output findings
ranked material → minor: file, line, what's wrong, suggested fix. Be direct. Do
not rubber-stamp; do not flag what gofmt/go vet already enforce.
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.
- 8d ago First seen · 32 lines · 45 tokens per session scan A 4455b822205d
go-reviewer is an agent published in the GitHub repository jdanigo/hydraia (8 stars, last pushed 18d ago), licensed MIT. It adds 45 tokens to every session and 407 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-31.
Other agents, from other repositories
go-reviewer
A specialist reviewer for Go code, the programming language created at Google. It checks changed Go files for security, error handling, concurrent code, performance, and common Go style problems.
go-reviewer
Go-specific code reviewer. Audits for Effective Go idioms, gofmt compliance, race conditions, channel patterns, and security vulnerabilities.
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…