A set of rules and examples for writing and reviewing committed Go tests, which are tests stored in a codebase and checked into version control. It explains how to shape test suites, name tests, add comments, and choose reference material for different scenarios.

Use it when writing or reviewing Go tests involving helpers, repeated cases, fixtures, examples, concurrency, invalid inputs, or conformance suites.

It gives maintainers a consistent standard for deciding what belongs in a Go test suite and how tests should be reviewed.

testing — Skill by notorious-ai

Install

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.

agentmods

npx agentmods add skills/notorious-ai/claude-plugins/testing

Any agent

npx skills add notorious-ai/claude-plugins --skill testing

Clone the repo

git clone --depth 1 https://github.com/notorious-ai/claude-plugins

Made for: Claude Code, Codex.

Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,747 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00068	$0.01747
Opus 5	$0.00034	$0.00873
Sonnet 5	$0.00014	$0.00349
Haiku 4.5	$0.00007	$0.00175

Measured 2d ago against content hash 24dfa035334b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 2d 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.

golang-dev/skills/testing/SKILL.md · 131 lines

How it starts

The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Committed Go Tests

Imitation is the method, split by role. The exemplar/ files are annotated verbatim snippets from the Go team's own packages; imitate them, because canon is the source and nothing bundled is canon of its own. WRITING tests: after go doc -all, match the package's disjoint symbol clusters to archetypes via exemplar/README.md and read ONLY the matched samples, as inspiration — generation is creative synthesis; the review loop carries the nuance load. REVIEWING or critiquing tests: read the whole exemplar corpus with its annotations — evaluation is discrimination; the corpus is your grading sense, calibrated by evaluator-cases.md, the rulings evaluators mis-graded before. Load references on scenario, not sooner:

references/helpers.md — a test wants a helper, a fake, or a dependency.
references/tables-and-subtests.md — cases repeat, or a t.Run forms.
references/fixtures.md — file inputs, long literals, malformed cases.
references/examples.md — an Example function is written, reviewed, or judged.
references/concurrency.md — goroutines, panics, races, invalid inputs.
references/harnesses.md — conformance suites and testing packages.

The contract and the golden hierarchy

Test freely while developing: throwaway tests, tailored executables, build-tagged experiments, runs under constrained CPU (a weak-runner flake is a contract failure too). None of it gets committed: committed _test.go files carry only the package's contract with its users, so a breaking change either fails the tests or amends them to state the new contract; unit tests are rapid iteration against a contract, not bug hunts.

The package's prose, the package doc and exported doc comments that godoc publishes and users rely on, is the most sacred part of its contract. Authority descends through exported signatures, code behavior, and unexported comments, down to the existing tests: the least golden thing in the room, never the standard. A test authored from the implementation mirrors it, bugs included; one authored from the prose holds the package to its promises. Drift is a finding, never silently absorbed: ask the owner, else side with prose unless the code moved deliberately, then fix the prose. Go-doc-first makes this operational: draft the test plan from go doc -all alone, no bodies, before opening source, so every collision is surfaced drift.

Read the full file on GitHub · 131 lines

Files

What ships with it

17 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.

Changes

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.

2d ago First seen · 131 lines · 68 tokens per session scan A 24dfa035334b

Subscribe to this mod's changes

testing is a skill published in the GitHub repository notorious-ai/claude-plugins (5 stars, last pushed 6d ago), licensed MIT. It adds 68 tokens to every session and 1,747 once invoked, about $0.0003 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.

Code review Git and workflow Testing

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens