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 rootwarp/claude-code-plugins-monorepo --skill go-testgit clone --depth 1 https://github.com/rootwarp/claude-code-plugins-monorepoWrote 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/rootwarp/claude-code-plugins-monorepo/go-test)<a href="https://agentmods.dev/skills/rootwarp/claude-code-plugins-monorepo/go-test"><img src="https://agentmods.dev/badge/skills/rootwarp/claude-code-plugins-monorepo/go-test/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/rootwarp/claude-code-plugins-monorepo/go-test"><img src="https://agentmods.dev/badge/skills/rootwarp/claude-code-plugins-monorepo/go-test.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.00000 | $0.00047 |
| Opus 5.5 | $0.00000 | $0.00019 |
| Sonnet 5.5 | $0.00000 | $0.00009 |
| Haiku 4.5 | $0.00000 | $0.00005 |
Grade A, and why
go-test 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.
What it actually says
/go-test
Run tests for the Go project.
Instructions
Run tests with verbose output and coverage:
go test -v -cover ./...
If tests fail, analyze the failures and suggest fixes.
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 · 14 lines · 0 tokens per session scan A 6ca8ba96d275
go-test is a skill published in the GitHub repository rootwarp/claude-code-plugins-monorepo (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 47 tokens. 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
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
zunit
Generate and run zunit tests for java-cli-app projects. Use when asked to create tests, write tests, add tests, or generate test files for a java-cli-app project. Triggers on "zunit", "write tests", "create tests", "add tests", "test this", "generate tests", or requests to test a java-cli-app application. Also trigger…
encore-go-testing
Write or run automated tests for Encore Go code with encore test and the standard library testing package. Covers isolated per-test databases, calling handlers directly, and testing.T patterns.
go-testing-mistakes
Guides the agent to avoid common Go testing mistakes when writing or reviewing test code. Covers test categorization (build tags, env vars, short mode), race detection, test execution modes (parallel, shuffle), table-driven tests, avoiding sleeps in tests, handling the time API deterministically, using httptest/iotest…
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…
go-testing
Use when writing or fixing Go tests — table-driven cases, parallel safety, helpers, fakes, fuzzing, deterministic time (testing/synctest), goroutine leak detection (goleak), HTTP handlers. Apply proactively when a function gets a new test or a test is flaky. Benchmark methodology: see go-benchmark.