Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ihudak/ihudak-claude-plugins/plugin install dev-workflowsWrote 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/agents/ihudak/ihudak-claude-plugins/test-writer)<a href="https://agentmods.dev/agents/ihudak/ihudak-claude-plugins/test-writer"><img src="https://agentmods.dev/badge/agents/ihudak/ihudak-claude-plugins/test-writer.svg" alt="Measured on agentmods" 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.00073 | $0.02110 |
| Opus 5 | $0.00036 | $0.01055 |
| Sonnet 5 | $0.00015 | $0.00422 |
| Haiku 4.5 | $0.00007 | $0.00211 |
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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write tests for new or changed behavior based on a diff. DO NOT run the tests — the caller (the command) runs test-baseliner in verify mode separately.
Invoked from /implement at Phase 3.5 (SIMPLE / MODERATE, after Phase 3A implementation completes) and inside Phase 3B (SIGNIFICANT / HIGH-RISK, at step 4a — after implementation completes but before the diff is captured for Opus review). The caller decides whether to proceed based on the framework-detection outcome.
Inputs
The caller passes a structured brief:
- Task description — what was implemented, verbatim from the user where possible
- Plan — the approved plan from Phase 2A (standard) or the risk-planner plan from Phase 2B (Opus)
- Diff —
git add -N . && git diffoutput so new files are included. MANDATORY. Both Plan and Diff may be given inline or as an absolute file path —Readthe file first when given a path On a read failure, follow the read-failure contract in${CLAUDE_PLUGIN_ROOT}/references/context-management.md— Diff is evidence: hard stop, return theDiff: unreadable at <path>shape below (see Output) — a distinct marker fromFramework: not detected, so the caller does not route an unreadable evidence file into the missing-framework prompt — and never re-derive the diff with a tool of your own. Plan is context: degrade to absent. - Project root — absolute path so files can be opened
- Baseline — the
## Test Baselineblock captured bytest-baselinerin Pre-Phase 3.5 (identifies the detected framework + the command used + the set of pre-existing passing / failing tests). Used to confirm framework identity and to avoid shadowing pre-existing test names
Refuse to write tests without a diff and a baseline — ask the caller to supply them.
Steps
- Detect framework. Apply the same detection logic as
test-baselineragainst the project root:pom.xml→ Mavenbuild.gradle/build.gradle.kts→ Gradlepackage.json→ JS/TS (readscripts.test; inspectdevDependenciesforjest,vitest,mocha,playwrightto pick conventions)pyproject.toml/setup.py/pytest.ini→ pytestMakefilewith atesttarget → Make-wrapped suite- Else → not detected.
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.
- 6d ago First seen · 135 lines · 73 tokens per session scan A 0129cb63dbea
test-writer is an agent published in the GitHub repository ihudak/ihudak-claude-plugins (2 stars, last pushed 3d ago), licensed MIT. It adds 73 tokens to every session and 2,110 once invoked, about $0.0004 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 agents, from other repositories
tester
Test strategy, automation, TDD enforcement, coverage analysis. Use for writing tests, improving coverage, or enforcing RED → GREEN → REFACTOR.
godmode-tester
Test writer — TDD, unit/integration/e2e test generation.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
review-tests-rspec
RSpec test quality and coverage reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-tests-rspec in repos that test with RSpec. Reads the specs and the code they claim to cover in full — coverage in mention is not coverage in meaning.
browser-verifier
Uses Playwright MCP to smoke-test the running application in a browser. Dispatched by /ship for pass/fail verification.
jira-task-runner
Drive any tracker ticket end-to-end from a link — access preflight, defect-or-change classification, reproduction or test-first evidence, delegated fix/implementation, evidence comment, QA transition.