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 clubpay/ronykit --skill go-testinggit clone --depth 1 https://github.com/clubpay/ronykitWrote 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/clubpay/ronykit/go-testing)<a href="https://agentmods.dev/skills/clubpay/ronykit/go-testing"><img src="https://agentmods.dev/badge/skills/clubpay/ronykit/go-testing/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/clubpay/ronykit/go-testing"><img src="https://agentmods.dev/badge/skills/clubpay/ronykit/go-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00090 | $0.01438 |
| Opus 5.5 | $0.00036 | $0.00575 |
| Sonnet 5.5 | $0.00018 | $0.00288 |
| Haiku 4.5 | $0.00009 | $0.00144 |
Grade A, and why
go-testing 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 23d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Testing
Tests are documentation that runs. Make them readable, deterministic, and fast.
Repo integration tests (mandatory — enforced by verify.sh)
Every method on every repository port in internal/repo/port.go must have an integration test in
internal/repo/integration_test/ using x/testkit against real Gnomock Postgres/Redis — not mocks.
Per method, cover:
- Happy path — creates/reads/updates as intended
- Not found — missing row / empty result
- Conflict — unique violation or constraint error
Read MCP architecture/integration-tests. Scaffold provides setup_test.go; add *_test.go files per domain. Run
go test ./internal/repo/integration_test/... and confirm green before treating the repo as done.
App unit tests (mandatory — enforced by verify.sh)
Every exported method on internal/app.App needs a unit test in internal/app/*_test.go. Test business rules with injected fakes/mocks
at the port boundary — not integration tests.
- Prefer a small in-memory fake of the repo port (a map behind the interface) over call-recording mocks: assert on the resulting state and the returned value, not on which port methods were called.
- Cover each business rule and each error path (
errors.Is(err, domain.ErrX)), not just the happy path. - Inject clocks and ID generators through
Appdependencies so expected values are fixed, hand-written constants.
When to use
- Adding tests for new Go behavior or covering a bug fix.
- Designing table-driven tests, subtests, fuzz tests, or benchmarks.
- Diagnosing flaky, slow, or order-dependent tests.
Conventions
- Table-driven + subtests. One
t.Run(tc.name, ...)per case so failures point at the exact scenario. - Arrange / Act / Assert. Keep the three sections visually distinct.
- Deterministic. No real clocks, randomness, network, or sleeps. Inject
time/IDs; use
context.Contextwith deadlines. - Parallel where safe.
t.Parallel()for independent cases (loop variables are per-iteration since Go 1.22 — notc := tc). Don't parallelize tests that share a database schema or global state. - Helpers call
t.Helper()so failures report the caller's line. t.Context()(Go 1.24+) for contexts that end with the test;t.Cleanupoverdeferin helpers.- Golden files for large outputs; gate updates behind a
-updateflag and review the diff before committing.
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.
- 23d ago Changed · +36 lines · +30 tokens per session ad5f74ea823c
- 1mo ago First seen · 113 lines · 60 tokens per session scan A b1aa8c5961c1
go-testing is a skill published in the GitHub repository clubpay/ronykit (38 stars, last pushed today), licensed BSD-3-Clause. It adds 90 tokens to every session and 1,438 once invoked, about $0.0004 per session on Opus 5.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 skills, from other repositories
test-runner
Run and triage Go tests with correct environment handling; produce compact, actionable failure summaries.
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
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.
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…