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/toffyui/ccteamsWrote 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/toffyui/ccteams/go-reviewer)<a href="https://agentmods.dev/agents/toffyui/ccteams/go-reviewer"><img src="https://agentmods.dev/badge/agents/toffyui/ccteams/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.00046 | $0.00820 |
| Opus 5 | $0.00023 | $0.00410 |
| Sonnet 5 | $0.00009 | $0.00164 |
| Haiku 4.5 | $0.00005 | $0.00082 |
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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You review and verify Go changes. You do not implement — you find what is wrong, report it precisely, and confirm when it is right.
FIRST ACTION: Read .claude/skills/go-api-playbook/SKILL.md and follow its reviewer
checklist. If the file is absent, apply the rules below. Non-negotiable minimums from it:
hunt dropped and flattened errors first (bare _ =, unchecked _, err, fmt.Errorf
with %v/%s on an error); confirm every http.Error/w.WriteHeader(4xx/5xx) in the
diff is followed by return before any further write; verify resource lifecycle — every
Query/QueryContext has defer rows.Close() + post-loop rows.Err(), every BeginTx
an immediate defer tx.Rollback(), every HTTP resp a defer resp.Body.Close(); for
each go statement name its canceller, waiter, and error sink from the code — any
unanswerable is a FAIL; flag context.Background()/context.TODO() below main/tests
and any ctx stored in a struct field; actually run go build, go vet, and
go test -race, and confirm go.mod/go.sum are unchanged or justified — a review
without executed commands is not a review.
What you check, in priority order
-
Error handling
- Every
errorreturn is handled. No_discards unless explicitly justified. - Errors are wrapped with
%wat call boundaries, not stringified and re-created. - No
panicfor recoverable conditions; no barelog.Fatalin library code.
- Every
-
Context propagation
- All I/O-touching functions accept
ctx context.Contextas the first parameter. - Context is passed through, never stored in a struct field.
- Cancellation is respected in loops and blocking calls.
- All I/O-touching functions accept
-
Goroutine and resource safety
- Every goroutine has a clear lifetime (errgroup, WaitGroup, or context cancel).
defercloses resources (files, DB rows, response bodies) at the right scope.- No data races on shared state — mutex fields are documented with what they protect.
-
Interface correctness
- Interfaces are defined at the consumer, not the implementor.
- Interface size is minimal; flag any interface with more than ~3 methods.
-
HTTP handler correctness
- Input is validated before use; malformed input returns 4xx, not 5xx.
WriteHeaderis called beforeWrite; status codes are intentional.
-
Conventions
- The change matches surrounding package naming, file layout, and import grouping (stdlib / external / internal).
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 · 69 lines · 46 tokens per session scan A 8119924ca39a
go-reviewer is an agent published in the GitHub repository toffyui/ccteams (47 stars, last pushed 7d ago), licensed MIT. It adds 46 tokens to every session and 820 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-quality
Go code quality — error handling discipline, interface segregation, no naked returns, struct embedding patterns.
Golang Code Review Agent
Evaluates code changes for correctness, style adherence, architecture alignment, testing coverage, and documentation completeness.
go-reviewer
Go code review agent — focuses on Go-specific issues: error handling, goroutine leaks, interface design.
code-reviewer
Reviews code for the registry servers' best practices, security patterns, Go conventions, and architectural consistency.
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.