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 Dankosik/go-service-template-rest --skill go-test-implementationgit clone --depth 1 https://github.com/Dankosik/go-service-template-restWrote 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/dankosik/go-service-template-rest/go-test-implementation)<a href="https://agentmods.dev/skills/dankosik/go-service-template-rest/go-test-implementation"><img src="https://agentmods.dev/badge/skills/dankosik/go-service-template-rest/go-test-implementation/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/dankosik/go-service-template-rest/go-test-implementation"><img src="https://agentmods.dev/badge/skills/dankosik/go-service-template-rest/go-test-implementation.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.00034 | $0.00351 |
| Opus 5 | $0.00017 | $0.00176 |
| Sonnet 5 | $0.00007 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
go-test-implementation 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 yesterday.
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.
What it actually says
Go Test Implementation
Write tests that reject wrong behavior through an observable independent of
the implementation being tested. Routine tests alongside production code stay
with go-coder; this method handles test-only work or non-routine controls.
Choose cases, fixtures, assertions, and commands while writing the tests from accepted product behavior and existing repository patterns. No pre-approved scenario, oracle, matrix, or separate test plan is required. Use the smallest deterministic layer that observes the claim. A source-string assertion proves behavior only when the exact text is itself the accepted output contract.
For a new integration scenario family, write one complete path through state creation, the operation, independent observation, and cleanup before expanding cases. Reuse that foundation while binding each case to its own inputs. An existing valid scenario already supplies this foundation; do not rebuild it. The active workflow decides when the scenario runs.
Load the reference selector only for a concrete problem with the proving layer, fixture, control, or command. Keep the result in test code and any existing task packet; add no proof-design artifact.
This method is complete when required tests and fixtures are written and their execution commands are recorded. The active workflow and Evidence Contract own validation timing and task completion. Missing test infrastructure is a final-validation input, not missing permission to write the tests.
What ships with it
4 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.
- yesterday Changed · +5 lines af1bd7c40c13
- 3d ago Changed · +2 lines · -8 tokens per session 23521fa2fd44
- 9d ago First seen · 29 lines · 42 tokens per session scan A 4db98a61a136
go-test-implementation is a skill published in the GitHub repository Dankosik/go-service-template-rest (7 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 351 once invoked, about $0.0002 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-31.
Other skills, from other repositories
go-testing
Use when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff. Also use when a user asks to write a test for a Go function, even if they don't mention specific patterns like table-driven tests or subtests. Does…
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…
Go Testing Patterns
Go testing with testing package, table-driven tests, subtests, benchmarks, test fixtures, httptest, and testify assertions.
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-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…
timeouts-and-async
Make Ginkgo specs interruptible and test asynchronous behavior — SpecContext/context.Context cancellable nodes, NodeTimeout/SpecTimeout/GracePeriod, the --timeout flag, Abort and SIGINT behavior, Gomega Eventually/Consistently (the func(g Gomega) form, .WithContext), and the defer GinkgoRecover() rule for goroutines.…