Borrowing it
Nothing to install: this file belongs to alex-ilgayev/MCPSpy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/alex-ilgayev/MCPSpy/main/.claude/skills/go-testing/SKILL.mdgit clone --depth 1 https://github.com/alex-ilgayev/MCPSpyWrote 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/alex-ilgayev/mcpspy/go-testing)<a href="https://agentmods.dev/skills/alex-ilgayev/mcpspy/go-testing"><img src="https://agentmods.dev/badge/skills/alex-ilgayev/mcpspy/go-testing.svg" alt="Measured on agentmods" 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.00040 | $0.00198 |
| Opus 5 | $0.00020 | $0.00099 |
| Sonnet 5 | $0.00008 | $0.00040 |
| Haiku 4.5 | $0.00004 | $0.00020 |
Grade A, and why
go-testing 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 8d 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 Testing Skill
Provides guidance and automation for Golang testing tasks in the MCPSpy project.
Testing Philosophy
- Use
requirelibrary for assertions that should stop test execution on failure - Use
assertlibrary for non-critical assertions where test should continue - Choose internal vs external package testing based on what needs to be tested
- Test internal functions by placing test files in the same package (no
_testsuffix) - Avoid creating externally facing functions solely for testing purposes
When to Use This Skill
- Running unit tests with
go test - Writing new test files and test cases
- Debugging and fixing failing tests
- Implementing test fixtures and mocks
- Improving test coverage for the MCPSpy project
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.
- 8d ago First seen · 25 lines · 40 tokens per session scan A 35d8d8aaef13
go-testing is a skill published in the GitHub repository alex-ilgayev/MCPSpy (516 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 198 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-30.
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…
softdev-loop
Go software-development loop — implement, test, vet; repeat until green.
cmd_go_test
Enforce TDD workflow for Go. Write table-driven tests first, then implement. Verify 80%+ coverage with go test -cover.
go-test
Skill "go-test" from rootwarp/claude-code-plugins-monorepo, covering /go-test and instructions.
golang-testing
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
golang-testing
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.