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 skills/clubpay/ronykit/go-testingnpx 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.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 | $0.00060 | $0.00921 |
| Opus 5 | $0.00030 | $0.00461 |
| Sonnet 5 | $0.00012 | $0.00184 |
| Haiku 4.5 | $0.00006 | $0.00092 |
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 4d 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 — 113 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.
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; capture loop variables (not needed in Go 1.22+, but be explicit if unsure). - Helpers call
t.Helper()so failures report the caller's line. - Golden files for large outputs; gate updates behind a
-updateflag.
Framework
Use standard testing with github.com/stretchr/testify (assert /
require). Prefer table-driven tests and t.Run subtests. Match surrounding
package style; do not introduce alternate assertion libraries.
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.
- 4d 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 3d ago), licensed BSD-3-Clause. It adds 60 tokens to every session and 921 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-08-30.
Other skills, from other repositories
sql-database-support
Guides classifying, gap-analyzing, and scaffolding support for a new SQL database in pREST (wire-compatible variants like TimescaleDB or new dialects). Use when adding database support, creating integration/ /, DIFFERENCES.md, adapters/ , per-DB docker-compose or GitHub workflows, or planning where config/app wiring…
prest-integration-tests
Guides writing and reviewing pREST Docker/network integration tests under integration/ so each request is human-readable via step comments or table-driven descriptions. Use when adding or editing integration//test.go, HTTP controller E2E coverage, make test-integration, test-integration-postgres…
ast-introspection
Use Go AST-aware analysis to enumerate symbols, extract signatures, and propose mechanically safe refactors (read-only by default).
build-run
Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.
ci-orchestrator
Run a CI-like pipeline locally (format, lint, vet, static-analysis, tests) and summarize per-step results with remediation guidance.
config-loader-helper
Diagnose configuration-related failures, enumerate required env vars, and guide safe local test setup (no secrets).