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.
npx agentmods add commands/gopherguides/gopher-ai/test-gengit clone --depth 1 https://github.com/gopherguides/gopher-aiWhat 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 | $0.00008 | $0.01572 |
| Opus 5 | $0.00004 | $0.00786 |
| Sonnet 5 | $0.00002 | $0.00314 |
| Haiku 4.5 | $0.00001 | $0.00157 |
Grade A, and why
test-gen 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 2d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
If $ARGUMENTS is empty or not provided:
Usage: /test-gen <target>
/test-gen pkg/auth/login.go— generate tests for a file/test-gen HandleAuthentication— generate tests for a function/test-gen pkg/utils/— generate tests for a package
Workflow: detect testing setup (testify/gomock/etc.) → analyze target → generate test cases (happy path, edge cases, errors) → create test file with table-driven patterns → self-review for coverage gaps.
Ask: "What file or function would you like me to generate tests for?"
If $ARGUMENTS is provided:
Generate comprehensive Go tests for the specified code with table-driven patterns and edge cases.
Loop Initialization
!if [ ! -x "${CLAUDE_PLUGIN_ROOT}/scripts/setup-loop.sh" ]; then echo "ERROR: Plugin cache stale. Run /gopher-ai-refresh (or refresh-plugins.sh) and restart Claude Code."; exit 1; else "${CLAUDE_PLUGIN_ROOT}/scripts/setup-loop.sh" "test-gen" "COMPLETE"; fi
Configuration
- Target:
$ARGUMENTS(file path or function name)
Steps
1. Detect Testing Environment
- testify:
go list -m all | grep testify - gomock:
go list -m all | grep gomock - mockery: look for
mockery.yaml/.mockery.yaml - Existing
_test.gopatterns
Also detect: file naming (*_test.go), package organization (same vs _test suffix), assertions (testify assert/require vs stdlib), mocking (gomock, mockery, hand-written).
2. Analyze Target
Read the target and extract: function signatures + parameters, return types and possible values, dependencies/interfaces, error conditions and returns, side effects (mutations, I/O, network), conditional branches and logic paths.
3. Identify Test Cases
| Category | Examples |
|---|---|
| Happy path | Basic functionality, expected returns, standard use cases |
| Edge cases | Empty inputs (nil/""/[]byte{}/empty slice); boundary values (0, -1, max int, empty string); single vs multiple elements; Unicode/special chars |
| Error scenarios | Invalid input types, out-of-range values, missing required parameters, context cancellation, I/O failures |
| Concurrency (if applicable) | Race conditions, deadlocks, parallel execution with t.Parallel() |
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.
- 2d ago First seen · 181 lines · 8 tokens per session scan A c5f96878aaeb
test-gen is a command published in the GitHub repository gopherguides/gopher-ai (21 stars, last pushed 2d ago), licensed MIT. It adds 8 tokens to every session and 1,572 once invoked, about $0.0000 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 commands, from other repositories
tests
Run the Week 4 backend test workflow. Build TESTARGS from $ARGUMENTS: use backend/tests when it is empty; prepend backend/tests when it starts with an option such as -k; otherwise use the supplied path or node ID as-is.
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
go-test
Go TDD workflow with table-driven tests.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
test-ts
Run TypeScript tests for Solana frontends and Anchor programs.