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.
git clone --depth 1 https://github.com/emaraschio/cursor-commandsWrote 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/commands/emaraschio/cursor-commands/write-unit-tests)<a href="https://agentmods.dev/commands/emaraschio/cursor-commands/write-unit-tests"><img src="https://agentmods.dev/badge/commands/emaraschio/cursor-commands/write-unit-tests/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/commands/emaraschio/cursor-commands/write-unit-tests"><img src="https://agentmods.dev/badge/commands/emaraschio/cursor-commands/write-unit-tests.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.00011 | $0.00395 |
| Opus 5.5 | $0.00004 | $0.00158 |
| Sonnet 5.5 | $0.00002 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
write-unit-tests 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
Overview
Write meaningful unit tests for target code. Full workflow: .cursor/skill-contracts/write-unit-tests/SKILL.md (user install: ~/.cursor/skill-contracts/write-unit-tests/SKILL.md).
Defaults
None. See skill for workflow defaults.
Steps
- Read
.cursor/skill-contracts/write-unit-tests/SKILL.mdfor the full agent contract; if that file is missing, read~/.cursor/skill-contracts/write-unit-tests/SKILL.md. - Execute the workflow in order; do not skip safety steps.
- Report outcomes per skill (summary, tables, or checklist as specified).
Anti-patterns
- Test behavior, not implementation trivia. Trigger: choosing what a unit test should assert. Wrong: asserting private internals, call counts, or getters that restate the code. Correct: assert observable behavior and public contracts. Reason: trivia tests break on harmless refactors and prove nothing about correctness.
- Mock only what you must. Trigger: the unit under test touches collaborators. Wrong: mocking every dependency, including pure logic you could call directly. Correct: mock external boundaries (network, clock, filesystem) and use real objects for the rest. Reason: over-mocking tests the mocks instead of the code and hides real integration breaks.
Examples
/write-unit-tests
Maintainers
Behavioral eval: .cursor/skill-contracts/write-unit-tests/eval/cases.md. Ship gate sections: A, S before changing SKILL.md or this command.
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 · 38 lines · 11 tokens per session scan A 01438790ae10
write-unit-tests is a command published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 16d ago), licensed MIT. It adds 11 tokens to every session and 395 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
check-coverage
Check test coverage, identify gaps, and suggest which code needs tests.
coding-flow
Light coding workflow: features, fixes, refactors, unit tests, etc.; scales small to large.
modernization-flow-testing
Phase 3 Testing (optional) of modernization-flow.
run-all-tests-and-fix
Execute the full test suite and systematically fix any failures, ensuring code quality and functionality.
pm-tests
List missing unit-test companions for core/changed sources. Do not write tests into the business tree unless the user confirms.
green-repo
Drive the whole repository to a verified-green baseline — typecheck, lint, tests, build — with authorized fixing of pre-existing debt.