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 agentmods add skills/patrick-fu/awesome-skills/write-unit-testnpx skills add patrick-fu/awesome-skills --skill write-unit-testgit clone --depth 1 https://github.com/patrick-fu/awesome-skillsWrote 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/patrick-fu/awesome-skills/write-unit-test)<a href="https://agentmods.dev/skills/patrick-fu/awesome-skills/write-unit-test"><img src="https://agentmods.dev/badge/skills/patrick-fu/awesome-skills/write-unit-test.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 | $0.00033 | $0.00445 |
| Opus 5 | $0.00016 | $0.00222 |
| Sonnet 5 | $0.00007 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
write-unit-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 5d 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
Write Unit Tests
Use this advisory skill for production product or business code. Prompt, skill, and agent-behavior evaluation need different methods.
Method
- Read the exported surface, its callers, nearby tests, and shared test utilities. State one caller-visible contract and the regression risk it guards.
- Write one test whose name states the expected outcome. Keep the decisive input visible at the call site; split distinct behaviors.
- Assert observable effects: returned values, public state, stable error types or codes, persistence, emitted events, rendered UI, or a boundary call when that call is itself the contract.
- Build the smallest realistic setup. Match real data and error shapes; isolate only the lowest true external boundary.
- For a regression or test-first change, confirm the test is red for the intended reason before relying on it.
- Run the focused test and relevant suite. Finish only when breaking the stated contract would fail the test while harmless internal refactoring would not.
Judgment
- Prefer exact domain outcomes and meaningful fields. Use full snapshots or full error messages only when the entire representation is the contract.
- Use a real dependency or small fake when its behavior matters. Mocks fit slow, flaky, costly, or external boundaries; verify collaborator calls only when the call is externally meaningful.
- Wait for the condition or event that proves async completion. Use a controlled clock or fixed delay only when timing itself is the contract.
- Keep contract-relevant fields in test doubles; partial mock shapes can hide downstream assumptions.
- Let builders remove noise while exposing the value that makes the case meaningful.
- Treat private-state access as a coupling signal. Keep test-only affordances in test utilities and production APIs product-driven.
- Match the repository's existing framework, naming, placement, and helper conventions.
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.
- 5d ago First seen · 48 lines · 33 tokens per session scan A 234ff0fee0c3
write-unit-test is a skill published in the GitHub repository patrick-fu/awesome-skills (57 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 445 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
run-helix-tests
Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues.
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
nunit-testing
Use when writing or modifying tests in NUnit's own test projects, or when making a behavioral change to production code that needs test coverage. Covers test structure, attribute choice, helper visibility, platform guards, and which test projects are real.
detect-flaky-tests
Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM lanes). For each newly-detected flaky test or infra issue, opens a GitHub issue with full evidence and a draft fix PR. Does…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
add-go-test
Write or extend Go unit tests in this repo. Use when the user asks to add or update Go tests.