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 commands/gokulkrishh/.cursor/write-unit-testsgit clone --depth 1 https://github.com/gokulkrishh/.cursorWhat 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.00000 | $0.00171 |
| Opus 5 | $0.00000 | $0.00086 |
| Sonnet 5 | $0.00000 | $0.00034 |
| Haiku 4.5 | $0.00000 | $0.00017 |
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 3d 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
Create comprehensive unit tests for the current code. Include:
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
Generate the test file with proper imports and setup according to the project's testing 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.
- 3d ago First seen · 35 lines · 0 tokens per session scan A f8d148df22fb
write-unit-tests is a command published in the GitHub repository gokulkrishh/.cursor (3 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 171 tokens. 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
tests
Run the Week 4 backend test workflow. Build TESTARGS from $ARGUMENTS: use backend/tests when it is empty; prepend backend/tests when it starts with an option such as -k; otherwise use the supplied path or node ID as-is.
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
go-test
Go TDD workflow with table-driven tests.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
test-ts
Run TypeScript tests for Solana frontends and Anchor programs.