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 n-n-code/n-n-code-skills --skill go-testing-with-testifygit clone --depth 1 https://github.com/n-n-code/n-n-code-skillsWrote 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/n-n-code/n-n-code-skills/go-testing-with-testify)<a href="https://agentmods.dev/skills/n-n-code/n-n-code-skills/go-testing-with-testify"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/go-testing-with-testify/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/n-n-code/n-n-code-skills/go-testing-with-testify"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/go-testing-with-testify.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.00079 | $0.01877 |
| Opus 5.5 | $0.00032 | $0.00751 |
| Sonnet 5.5 | $0.00016 | $0.00375 |
| Haiku 4.5 | $0.00008 | $0.00188 |
Grade A, and why
go-testing-with-testify 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Testing With Testify
Turn a concrete behavior claim into useful Go test evidence. Preserve the repository's Go version, test framework, and supported execution environment.
Route And Select Activity
- Implement or harden: edit the requested tests and any explicitly covered production seam. A test request does not automatically authorize an unrelated production refactor, new dependency, or external service.
- Review: inspect tests and report prioritized findings, evidence, and consequences. Do not edit files or require remediation to complete a review.
- Diagnose: reproduce the named failure in scope, distinguish a product defect from a test-apparatus defect, then fix it when the request includes repair.
Use coding-guidance-go for production Go or non-testify tests. Preserve
Ginkgo, Gomega, go-cmp-only, and other intentional stacks. Module bootstrap or
test-tool installation is separate from test authoring.
Add tester-mindset when claims, oracles, or test strategy are still unclear.
Add backend-guidance or backend-systems-guidance only when a service,
repository, queue, or other backend boundary needs that design guidance.
Use security first for a security-led review and add
security-identity-access when its identity scope applies. Routine tests of an
already-defined permission rule can remain here.
Workflow
- Read the scoped tests, implementation,
go.mod, fixtures, and relevant repository instructions. Identify the Go and testify versions, local test command, helpers, and available dependencies. - Name the behavior claim, oracle, and smallest seam that can reveal a defect. Pure logic needs a unit check; protocol, query, serialization, or lifecycle behavior may need a real boundary. Passing checks support only their scope.
- Preserve the existing test shape when it is clear. Use table-driven subtests when cases share setup and assertions; use separate tests when they do not. Introduce helpers, fakes, mocks, or suites only for a concrete benefit.
- For implementation, exercise the real code and assert the behavior being claimed. For review, assess these choices without rewriting the tests.
- Validate the narrowest changed test or package, for example
go test ./path/to/pkg -run '^TestName$' -count=1. Add race checks, repetition, shuffle, or integration runs when the failure mode needs them. - Inspect failures before changing assertions, retry counts, or timeouts. Report the exact evidence and remaining uncertainty.
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 Changed · -226 lines · +4 tokens per session 4a769cfa69a0
- 1mo ago First seen · 383 lines · 75 tokens per session scan A 4fbe5a7251ab
go-testing-with-testify is a skill published in the GitHub repository n-n-code/n-n-code-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 1,877 once invoked, about $0.0003 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-31.
Other skills, from other repositories
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…
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…
unit-test
A Go testing workflow for writing unit tests: small tests that check individual functions or components. It supports table-driven cases, where many inputs and expected results are organised in one test, and subtests.
fuzzing-test
A Go testing guide for generating fuzz tests, which repeatedly try varied inputs to find crashes and unexpected behavior. It first checks whether the code is suitable for fuzzing.
golang-testing-patterns
Modern Go testing patterns including table-driven tests, subtests, test organization, and best practices. Use when writing or refactoring tests, implementing test coverage, or when the user asks about Go testing approaches.
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.