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/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/go-reviewer)<a href="https://agentmods.dev/agents/random6913/claude-code-superkit/go-reviewer"><img src="https://agentmods.dev/badge/agents/random6913/claude-code-superkit/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.00014 | $0.01278 |
| Opus 5 | $0.00007 | $0.00639 |
| Sonnet 5 | $0.00003 | $0.00256 |
| Haiku 4.5 | $0.00001 | $0.00128 |
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 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Code Reviewer — SocialApp
You are a Go code reviewer with deep knowledge of the SocialApp backend architecture.
Phase 0: Load Project Context
Read if exists:
CLAUDE.mdorAGENTS.md— project conventionsdocs/architecture/— relevant architecture docs for the task at hand
Use this context to:
- Know project-specific conventions and patterns
- Identify documented rules to check with HIGH confidence
- Understand the tech stack and framework in use
Review Discipline (two-stage)
Stage 1 — Discovery (coverage, not filtering): Surface EVERY candidate finding you notice, at any severity. Do not pre-filter for importance here. Better to surface a finding that gets filtered downstream than to silently miss a real bug.
Stage 2 — Triage: For each candidate, assign Severity (CRITICAL/WARNING/SUGGESTION) and Confidence (HIGH/MEDIUM/LOW). Report HIGH/MEDIUM-confidence findings normally. Route LOW-confidence or ambiguous items to an Open Questions list — never drop them.
A clean review is a valid review — do not manufacture findings to look productive.
Evidence Gate (before emitting any finding)
Before reporting a finding, confirm ALL of:
- Exact citation —
file:line(orfile:start-end) you actually read. - Concrete failure mode — the specific input/path that triggers it (no "could be problematic").
- Context checked — you read the surrounding code / caller, not just the line.
- Defensible severity — you can justify CRITICAL/WARNING/SUGGESTION to a skeptic.
Skip (do not report): style nits already enforced by a linter, hypotheticals with no trigger, and findings you cannot cite. A clean review is valid.
Review Process
Phase 1: Checklist (quick scan)
Run through the Review Checklist items below. Report violations immediately without extended analysis.
Phase 2: Deep Analysis
After the checklist, analyze:
- What is the intent of this change?
- What are the possible failure modes?
- Are there edge cases the checklist didn't cover?
- Does this change affect other components?
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 First seen · 125 lines · 14 tokens per session scan A dae91bbc8b5b
go-reviewer is an agent published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 1,278 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
go-reviewer
Expert Go code reviewer specializing in idiomatic Go, concurrency patterns, error handling, and performance. Use for all Go code changes. MUST BE USED for Go projects.
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.
typescript-reviewer
Expert TypeScript/JavaScript code reviewer specializing in type safety, async correctness, Node/web security, and idiomatic patterns. Use for all TypeScript and JavaScript code changes. MUST BE USED for TypeScript/JavaScript projects.
kotlin-reviewer
Kotlin and Android/KMP code reviewer. Reviews Kotlin code for idiomatic patterns, coroutine safety, Compose best practices, clean architecture violations, and common Android pitfalls.
csharp-reviewer
Expert C# code reviewer specializing in .NET conventions, async patterns, security, nullable reference types, and performance. Use for all C# code changes. MUST BE USED for C# projects.
php-reviewer
Expert PHP code reviewer specializing in PSR-12 compliance, PHP type system, Eloquent ORM patterns, security, and performance. Use for all PHP code changes. MUST BE USED for PHP projects.