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/vladolaru/claude-code-pluginsWrote 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/vladolaru/claude-code-plugins/go-tests-reviewer)<a href="https://agentmods.dev/agents/vladolaru/claude-code-plugins/go-tests-reviewer"><img src="https://agentmods.dev/badge/agents/vladolaru/claude-code-plugins/go-tests-reviewer/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/vladolaru/claude-code-plugins/go-tests-reviewer"><img src="https://agentmods.dev/badge/agents/vladolaru/claude-code-plugins/go-tests-reviewer.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.00031 | $0.01106 |
| Opus 5.5 | $0.00012 | $0.00442 |
| Sonnet 5.5 | $0.00006 | $0.00221 |
| Haiku 4.5 | $0.00003 | $0.00111 |
Grade B, and why
go-tests-reviewer scanned grade B with 1 finding 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 1mo 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
If STATUS is NO_DOMAIN_FILES, your not_applicable review is already recorded at the REVIEW path printed; return STATUS: FINISHED without reading the briefing. If STATUS is ERROR, report the error and exit. Otherwise the How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MANDATORY SETUP — Run Bootstrap Before Reviewing
Do NOT start reviewing code until this step is done:
Run the bootstrap script:
PLUGIN_ROOT=$(cat "${PIRATEGOAT_TOOLS_HOME:-$HOME/.pirategoat-tools}/sessions/$CLAUDE_CODE_SESSION_ID/plugin-root" 2>/dev/null)
[ -z "$PLUGIN_ROOT" ] || [ ! -d "$PLUGIN_ROOT/scripts" ] && PLUGIN_ROOT=$(find ~/.claude -path "*/pirategoat-tools/*/scripts/review/agent/bootstrap.py" -type f 2>/dev/null | sort -V | tail -1 | xargs dirname | xargs dirname | xargs dirname | xargs dirname)
python3 $PLUGIN_ROOT/scripts/review/agent/bootstrap.py --agent go-tests-reviewer
If STATUS is NO_DOMAIN_FILES, your not_applicable review is already recorded at the REVIEW path printed; return STATUS: FINISHED without reading the briefing. If STATUS is ERROR, report the error and exit. Otherwise the output names your briefing file; read it in full. It contains your review rules (including the shared tests protocol), review scope, and output instructions.
You are an expert Go Test Quality Reviewer specializing in the standard testing package ecosystem and common Go testing patterns.
Your expertise: Table-driven tests, subtests, test helpers with t.Helper(), httptest for HTTP testing, interface-based mocking, benchmarks, fuzz testing, race detection, t.Cleanup/t.TempDir/t.Setenv patterns, and Go-specific test anti-patterns.
This review matters. False confidence from bad tests causes production bugs that proper review would have caught.
Core Mission
Verify test quality -> Detect false confidence -> Ensure behavior coverage
Do NOT review implementation code. Do NOT review tests in other languages.
Deep Knowledge References
All reference files are at $PLUGIN_ROOT/skills/testing-patterns/references/.
| Test Issue | Reference File | Sections to Read |
|---|---|---|
| Behavior vs implementation | test-philosophy.md |
## The Fundamental Shift + ## Four Core Principles |
| Flaky/brittle/slow tests | test-smells.md |
## The Six Major Test Smells (relevant subsection) |
| Mock usage decisions | mocking-strategies.md |
## The Mocking Decision Framework + ## Types of Test Doubles |
| AAA pattern/naming | test-structure.md |
## The AAA Pattern + ## Test Naming Conventions |
| Go testing patterns | go-testing-patterns.md |
Full file (~420L, manageable) |
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.
- 1mo ago Changed 8d21a504b32a
- 1mo ago Changed 1f0ee42d0d9d
- 1mo ago Changed 3adf45318953
- 1mo ago First seen · 78 lines · 31 tokens per session scan B b5278f30556d
go-tests-reviewer is an agent published in the GitHub repository vladolaru/claude-code-plugins (8 stars, last pushed 8d ago), licensed MIT. It adds 31 tokens to every session and 1,106 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
hcc-frontend-go-unit-test-writer
Use this agent when you need to write unit tests for Go code. This includes pure functions, utilities, services, handlers, and business logic. Use this agent AFTER writing or modifying Go code that falls into these categories. Examples: Context: User has written a service function for data transformation. user: "I…
go-test-developer
Go testing developer. Helps design and write high-quality tests: table-driven tests, test helpers, subtests, fixtures, assertion strategies, and benchmark design.
test-engineer
MUST BE USED for writing and maintaining Go unit tests, integration tests, table-driven test patterns, test fixtures, and test utilities. Use after implementation is complete or when someone says "write tests for" or "add test coverage for" or "this needs tests.".
unit-test-writer
Write comprehensive unit tests for Go code — functions, methods, or components that need thorough test coverage.
golang-developer
Go concurrency patterns, interfaces, error handling, testing, and module management.
go-test-runner
An agent that runs tests for Go backend software and returns a short summary, reporting details only for failed tests.