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 fusengine/agents --skill go-testing-qualitygit clone --depth 1 https://github.com/fusengine/agentsWrote 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/fusengine/agents/go-testing-quality)<a href="https://agentmods.dev/skills/fusengine/agents/go-testing-quality"><img src="https://agentmods.dev/badge/skills/fusengine/agents/go-testing-quality/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/fusengine/agents/go-testing-quality"><img src="https://agentmods.dev/badge/skills/fusengine/agents/go-testing-quality.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.00040 | $0.00932 |
| Opus 5.5 | $0.00016 | $0.00373 |
| Sonnet 5.5 | $0.00008 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
go-testing-quality 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 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.
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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Testing & Quality
Idiomatic, 2026-current testing and quality practices for Go, built on the standard
testing package with testify where it adds clarity.
Use when:
- Writing unit tests for Go code (table-driven, subtests)
- Adding assertions or mocks with
testify(assert/require/mock) - Writing fuzz tests, benchmarks, or example tests
- Measuring coverage (
go test -cover) or chasing race conditions (-race) - Profiling / optimizing with pprof or setting up PGO
- Reviewing an existing Go test suite for quality gaps
Do NOT use for:
- Project layout, routing, DB wiring, DI — use
go-architecture - SOLID line-limit / interface enforcement — use
fuse-solid:solid-go - Non-Go test suites (Pest, Vitest, Jest, cargo test) — use the matching expert
- Security scanning / CVE audit — use
fuse-security
Decision Map
| Goal | Load |
|---|---|
| Write the standard Go test (table-driven + subtests) | table-driven.md |
| Assertions and mocks with testify | testify-mocks.md |
| Fuzzing, benchmarks, example tests | fuzzing-benchmarks.md |
| Coverage, race detector, pprof, PGO | coverage-profiling.md |
| A complete, runnable test file to copy | templates/table-test.md |
Core Practices (2026)
- Table-driven tests are the idiom. Define a slice of cases, loop, and run
each as a subtest with
t.Run(tc.name, …)for isolation and readable output. testifyis the de-facto assertion/mock standard.assertfor soft checks,requireto abort on failure,mockfor hand-written mocks,suitefor setup/teardown groups. It is maintained at v1 (no breaking v2). Source: https://pkg.go.dev/github.com/stretchr/testify- Fuzzing is native since Go 1.18 (
func FuzzXxx(f *testing.F)), and finds edge cases table tests miss. - Always run
-racein CI. The race detector catches data races that are otherwise nondeterministic and unreproducible. - Measure before optimizing. Benchmarks (
go test -bench) + pprof profiles guide real changes; PGO feeds a production profile back into the compiler.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 81 lines · 40 tokens per session scan A 10668323e4f8
go-testing-quality is a skill published in the GitHub repository fusengine/agents (33 stars, last pushed 8d ago), licensed MIT. It adds 40 tokens to every session and 932 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
r-testthat
Best practices for writing R package tests with testthat version 3+. Use this skill when writing or organizing tests for an R package or when improving existing tests that use testthat. It covers test structure and expectations, self-sufficient test design, proper cleanup with withr, fixtures, mocking external…
craft-pest
Testing Craft CMS 5 plugins and modules with Pest — test isolation, database safety, and the markhuot/craft-pest-core harness. ALWAYS load when writing, running, fixing, or reviewing tests for a Craft plugin or module, and whenever a suite touches a real Craft install. Covers why rollback is opt-in, tests/Pest.php +…
test-go
Write, review, and improve Go test code for this project. Use whenever generating, reviewing, or modifying Go tests - including when invoked by the Tester agent, the /test prompt, or any test-related request. Covers table-driven tests, subtests, t.Parallel(), test helpers with t.Helper(), error assertions via…
go-test
When the user wants to design, implement, debug, or optimize Go tests using the standard testing package, testify, and related Go ecosystem libraries. Use when the user mentions "go test," "table-driven tests," "t.Run," "subtests," "testify," "require / assert," "go test -race," "go test -bench," "go test -fuzz,"…
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…
golang-test-review
Use when reviewing Go test code (new or changed test.go files, test harnesses, fixtures, or test tooling) for a Go-test-expert pass — behavior-over-surface, determinism, parallel-safety, build-tag correctness, and harness reuse. Complements the general code-reviewer with test-specific rigor.