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 MCKRUZ/claude-code-sdlc --skill test-writergit clone --depth 1 https://github.com/MCKRUZ/claude-code-sdlcWrote 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/mckruz/claude-code-sdlc/test-writer)<a href="https://agentmods.dev/skills/mckruz/claude-code-sdlc/test-writer"><img src="https://agentmods.dev/badge/skills/mckruz/claude-code-sdlc/test-writer/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/mckruz/claude-code-sdlc/test-writer"><img src="https://agentmods.dev/badge/skills/mckruz/claude-code-sdlc/test-writer.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.00052 | $0.00406 |
| Opus 5.5 | $0.00021 | $0.00162 |
| Sonnet 5.5 | $0.00010 | $0.00081 |
| Haiku 4.5 | $0.00005 | $0.00041 |
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 21d 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
A test that can't fail when the underlying business logic changes is wrong. Each test encodes why a behavior matters, not just what it does, and ties back to a spec acceptance check.
Procedure
- Anchor to the spec. Open
specs/NNNN-name.md; each acceptance check should map to at least one test. Name tests so the mapping is legible (MethodName_Scenario_ExpectedResult). - For a bug fix, reproduce first. Write the test that fails because of the bug, watch it fail, then fix. The fix isn't done until that test passes.
- Prefer real implementations over mocks. Use the project's integration harness ({{e.g. WebApplicationFactory + in-memory DB}}) for pipeline behavior. Mock only external services (HTTP, third-party APIs) and time. Never mock the thing under test or value objects.
- Cover the edges named in the spec — the burst window, the null path, the boundary value — not just the happy path.
- Run the suite (
{{TEST_CMD}}) and confirm green before you consider it done. The Stop hook will block the turn anyway if it's red — beat it to the check.
Done when
- Every acceptance check has a covering test, named to show the mapping.
- New code meets the coverage bar ({{e.g. 80%}}).
- For a bug fix: the reproducing test existed, failed, and now passes.
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.
- 21d ago First seen · 32 lines · 52 tokens per session scan A f9979f3403ae
test-writer is a skill published in the GitHub repository MCKRUZ/claude-code-sdlc (8 stars, last pushed 9d ago), licensed MIT. It adds 52 tokens to every session and 406 once invoked, about $0.0002 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-26.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.