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 skills add mickeyyaya/evolve-loop --skill golang-test-reviewgit clone --depth 1 https://github.com/mickeyyaya/evolve-loopWrote 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/skills/mickeyyaya/evolve-loop/golang-test-review)<a href="https://agentmods.dev/skills/mickeyyaya/evolve-loop/golang-test-review"><img src="https://agentmods.dev/badge/skills/mickeyyaya/evolve-loop/golang-test-review/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/skills/mickeyyaya/evolve-loop/golang-test-review"><img src="https://agentmods.dev/badge/skills/mickeyyaya/evolve-loop/golang-test-review.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.00070 | $0.01134 |
| Opus 5 | $0.00035 | $0.00567 |
| Sonnet 5 | $0.00014 | $0.00227 |
| Haiku 4.5 | $0.00007 | $0.00113 |
Grade A, and why
golang-test-review 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 6d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/evo:golang-test-review
A focused Go-test-engineering review. Run it over the changed *_test.go files
(and any test harness / fixtures / test tooling) after writing tests and
before merge. It does not replace code-reviewer — it adds the test-specific
lens that general review misses.
How to run
- Identify the changed test surface:
git diff --stat <base>...HEAD -- '*_test.go' 'go/test/**' 'go/cmd/testlatency/**'. - Read each changed test file and score it against the checklist below.
- Report findings by severity (CRITICAL / HIGH / MEDIUM / LOW), each with
file:line, the rule violated, and a concrete fix. End with a verdict: APPROVE (no CRITICAL/HIGH) / CHANGES-REQUESTED.
Checklist
1. Behavior over surface (the highest-signal rule)
- Does the test pin the invariant under change, or just re-walk lines for coverage? A test that would still pass if the behavior broke is a no-op — flag it CRITICAL. (AGENTS.md Rule 9.)
- Are assertions specific (exact value / error) rather than "not nil" / "len > 0" where an exact check is possible?
- Negative + edge cases present, not only the happy path?
2. Determinism (non-negotiable)
- No dependence on ambient state: live repo,
$HOME, real clock, network,.evolve/runs/. Tests build isolated state (t.TempDir()+git init, or the sharedfixtures.NewWorkspace). - No real
time.Sleepfor synchronization where an injected clock / channel / poll-with-deadline would be deterministic. Real sleeps belong only in build-tagged integration/e2e tiers. - No ordering dependence between tests; no shared mutable package globals.
3. Parallel-safety
t.Parallel()is present where safe — BUT never combined witht.Setenv(panics) or shared-mutable-state tests.- Subtests that capture a loop variable are Go-1.22-safe or copy the variable.
-raceclean (the suite runs with-race).
4. Build-tag / cost-axis correctness (this repo's two-axis model)
- Slow tests (real subprocess: git/gh/tmux/bash; real timing) carry
//go:build integrationor//go:build e2eand are NOT in the fast default. - Self-containment: an untagged (fast) test must not reference a symbol defined only in a tagged file — the default build would break. Shared helpers the fast suite needs live in an untagged file.
- Tag sits at the top, followed by a blank line, before
package.
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.
- 6d ago First seen · 86 lines · 70 tokens per session scan A c6de70bc7620
golang-test-review is a skill published in the GitHub repository mickeyyaya/evolve-loop (5 stars, last pushed today), licensed Apache-2.0. It adds 70 tokens to every session and 1,134 once invoked, about $0.0003 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 skills, from other repositories
go-testing-quality
Use when writing or reviewing Go tests, adding coverage, benchmarking, or profiling a Go program. Not for CI/lint wiring (go-tooling-security) or non-Go tests.
golang-testing
Provides a comprehensive guide for writing production-ready Golang tests. Covers table-driven tests, test suites with testify, mocks, unit tests, integration tests, benchmarks, code coverage, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, memory leaks, CI with GitHub…
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-stretchr-testify
Comprehensive guide to stretchr/testify for Golang testing. Covers assert, require, mock, and suite packages in depth. Use when writing tests with testify, creating mocks, setting up test suites, or choosing between assert and require. Covers testify assertions, mock expectations, argument matchers, call verification…
setup
Wire Ginkgo into a Go package — install the ginkgo CLI and Ginkgo+Gomega, ginkgo bootstrap to generate the suitetest.go (TestXxx/RegisterFailHandler(Fail)/RunSpecs), the package xxxtest convention, dot-import alternatives (aliased import, dsl/ subpackages, --nodot), ginkgo generate, and testing.T interop via…
eng-test-conventions
Go test-shape discipline for Compozy. Use when writing or editing test.go under cmd or internal after test placement is justified. Do not use for non-Go tests, fixture-only changes, or as a replacement for eng-consolidate-test-suites.