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 sgaunet/claude-plugins --skill go-tddgit clone --depth 1 https://github.com/sgaunet/claude-pluginsWrote 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/sgaunet/claude-plugins/go-tdd)<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/go-tdd"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/go-tdd/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/sgaunet/claude-plugins/go-tdd"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/go-tdd.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.00021 | $0.01865 |
| Opus 5.5 | $0.00008 | $0.00746 |
| Sonnet 5.5 | $0.00004 | $0.00373 |
| Haiku 4.5 | $0.00002 | $0.00186 |
Grade A, and why
go-tdd 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 22d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go TDD Implementation
Implement a Go feature using strict RED → GREEN → REFACTOR TDD methodology, with Context7 MCP integration for up-to-date library documentation at each phase.
Arguments
$argument: Feature description and optional flags (required)
Flags
| Flag | Short | Effect |
|---|---|---|
--skip-lint |
-l |
Skip golangci-lint in Phase 5 |
--skip-refactor |
-r |
Skip Phase 4 refactoring |
--dry-run |
-n |
Show plan only, no file writes |
--force |
-f |
Skip all user confirmations |
Error Handling
| Error | Action |
|---|---|
No go.mod found |
Abort with message: "Not a Go project — no go.mod found" |
| Context7 unavailable | Warn and continue without doc validation |
| Tests won't compile | Display errors, attempt fix (max 2 retries), then ask user |
| Tests fail in GREEN phase | Attempt fix (max 2 retries), then ask user |
| Lint failure | Attempt auto-fix, re-run, then ask user |
| Build failure | Display errors, abort |
Process
Phase 1: Discovery & Documentation (Automatic)
-
Parse flags from
$argument:- Extract feature description (everything before flags)
- Detect
--skip-lint/-l,--skip-refactor/-r,--dry-run/-n,--force/-f
-
Validate Go project:
- Check
go.modexists — if not, abort: "Not a Go project — no go.mod found" - Read
go.modto identify module name and Go version
- Check
-
Analyze project structure:
- Scan existing packages, test patterns, coding conventions
- Identify existing test helpers or shared fixtures
- Note the project's import style, error handling patterns, naming conventions
- Check existing
*_test.gofiles for package naming: flag any white box tests (package <pkgname>without_testsuffix) for potential conversion
-
Identify libraries needed for the feature:
- Determine which standard library packages are involved
- Determine which third-party libraries are needed
-
Fetch Context7 documentation for each library:
- Call
mcp__context7__resolve-library-idto get the library ID - Call
mcp__context7__query-docswith a query specific to the feature being implemented - If Context7 is unavailable, warn and continue without doc validation
- Call
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.
- 22d ago First seen · 208 lines · 21 tokens per session scan A a62a074c4fb5
go-tdd is a skill published in the GitHub repository sgaunet/claude-plugins (16 stars, last pushed 8d ago), licensed MIT. It adds 21 tokens to every session and 1,865 once invoked, about $0.0001 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-25.
Other skills, from other repositories
testing-go
Writes tests following TDD (using go test, testify, and rapid) best practices. Use when writing unit tests, integration tests, or table-driven tests in Go.
golang-testing
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
dotnet-test
This skill should be used when running .NET tests selectively with a build-first, test-targeted workflow. Use it for running tests with xUnit focus.
dotnet-verify
This skill should be used when working with Verify snapshot tests in .NET projects. Use when updating verified snapshots after intentional code changes, accepting new snapshots, discovering verify tests, or troubleshooting snapshot mismatches. Trigger phrases include "verify tests", "update snapshots", "accept…
tdd-workflow
Enforce practical Test-Driven Development for code changes in Go services. Use for new features, bug fixes, refactors, API changes, and new modules. Requires Red-Green-Refactor evidence, defect-hypothesis-driven tests, killer cases, and coverage gates (line + risk-path).
go-testing
Use when writing, reviewing, or running Go tests in test.go files — writing tests for a Go package, adding table-driven tests with t.Run subtests, testing a Go HTTP handler with httptest, adding a Go fuzz test or seed corpus, running or choosing go test flags (-race, -fuzz, -fuzztime), or deciding whether to use…