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/amelmo/loadout/test-writernpx skills add AmElmo/loadout --skill test-writergit clone --depth 1 https://github.com/AmElmo/loadoutWhat 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.00013 | $0.00256 |
| Opus 5 | $0.00006 | $0.00128 |
| Sonnet 5 | $0.00003 | $0.00051 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
test-writer 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.
What it actually says
Test Writer
Given a function, hook, or module, generate comprehensive unit tests:
- Happy path: Normal usage with expected inputs and outputs
- Edge cases: Empty inputs, boundary values, max/min, unicode, null/undefined
- Error paths: Invalid inputs, network failures, timeout scenarios
- Async behavior: Promise resolution, rejection, loading states
- Integration: How the unit interacts with its direct dependencies
Rules
- Use
vitestwithdescribe/itblocks - Mock external dependencies with
vi.mock()— never mock the unit under test - Use
@testing-library/reactandrenderHook()for React hooks - Each test should verify exactly one behavior
- Use descriptive test names:
it("returns empty array when input is null") - Include setup/teardown in
beforeEach/afterEachwhen shared across tests - Aim for 90%+ branch coverage on the unit under test
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 · 27 lines · 13 tokens per session scan A 48ceb5e8876b
test-writer is a skill published in the GitHub repository AmElmo/loadout (9 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 256 once invoked, about $0.0001 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.
Other skills, from other repositories
verify
Self-healing verification loop (test → clippy → fmt).
backseat-driver-testing
Testing strategies for Calva Backseat Driver MCP tools. Use when: Testing Backseat Driver, validating tool updates, testing structural editing workflows, verifying REPL evaluation with who-tracking, testing shadow-cljs runtime discovery and targeting, testing output log filtering, testing load-file tool, smoke testing…
coverage
Compute code coverage for active track or module. Targets 95%+ coverage with report and justification for uncovered lines. Complements TDD workflow.
test-generator
完整：uv run ruff check src/; uv run mypy src/ --ignore-missing-imports; uv run bandit -r src/ -ll.
testing-strategy
Follow the testing pyramid — more unit tests, fewer integration tests, even fewer e2e tests.
testing
Provides testing patterns for FastAPI endpoints and Svelte 5 components using pytest and Vitest. USE WHEN the user asks to "write tests for a FastAPI endpoint", "test a Svelte component", "set up pytest fixtures", "configure Vitest for SvelteKit", "mock dependencies in tests", "test SSE streaming endpoints", or works…