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 emaraschio/cursor-commands --skill write-unit-testsgit 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/skills/emaraschio/cursor-commands/write-unit-tests)<a href="https://agentmods.dev/skills/emaraschio/cursor-commands/write-unit-tests"><img src="https://agentmods.dev/badge/skills/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/skills/emaraschio/cursor-commands/write-unit-tests"><img src="https://agentmods.dev/badge/skills/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.00413 |
| Opus 5.5 | $0.00004 | $0.00165 |
| Sonnet 5.5 | $0.00002 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00041 |
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
Create comprehensive unit tests for the current code and generate the test file with proper imports and setup according to the project's testing conventions.
Steps
- Test Coverage
- Test all public methods and functions
- Cover edge cases and error conditions
- Test both positive and negative scenarios
- Aim for high code coverage
- Test Structure
- Use the project's testing framework conventions
- Write clear, descriptive test names
- Follow the Arrange-Act-Assert pattern
- Group related tests logically
- Test Cases to Include
- Happy path scenarios
- Edge cases and boundary conditions
- Error handling and exception cases
- Mock external dependencies appropriately
- Test Quality
- Make tests independent and isolated
- Ensure tests are deterministic and repeatable
- Keep tests simple and focused on one thing
- Add helpful assertion messages
Write Unit Tests Checklist
- Tested all public methods and functions
- Covered edge cases and error conditions
- Tested both positive and negative scenarios
- Used the project's testing framework conventions
- Written clear, descriptive test names
- Followed the Arrange-Act-Assert pattern
- Included happy path scenarios
- Included edge cases and boundary conditions
- Mocked external dependencies appropriately
- Made tests independent and isolated
- Ensured tests are deterministic and repeatable
Guardrails
- Test observable behavior and public contracts, not implementation trivia.
- Mock only external boundaries (network, clock, filesystem); use real objects for the rest.
- Do not commit, push, merge, or run destructive commands without explicit user consent.
- Do not print, log, or commit secrets or credentials found in the code or test fixtures; flag any exposure instead.
What ships with it
3 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.
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 · 52 lines · 11 tokens per session scan A 7b63769b9c64
write-unit-tests is a skill published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 5d ago), licensed MIT. It adds 11 tokens to every session and 413 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-09-03.
Other skills, from other repositories
iterate-agent-harness
Turn an agent failure (premature stop, false completion, gamed check, missed file) into a rule, hook, or CI guard with a regression test. Use when "the agent stopped early again", "it gamed the test", or "add a guard so this doesn't recur".
review-coverage
Use when the user asks for a coverage review, test coverage analysis, coverage gap analysis, uncovered code review, or wants to know what new/changed Go code is missing tests. Runs go test -coverprofile against the resolved scope and reports uncovered functions in changed Go files, grouped by package, with severity…
testing
Use when the user writes or runs tests, sets up the Test Runner, needs Edit Mode or Play Mode tests, test assembly definitions, mocks, or async tests, or runs tests in CI. Covers Unity Test Framework, NUnit assertions, UnityTest coroutines, async Task tests, and test asmdef setup.
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
data-quality-frameworks
Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.