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.
git clone --depth 1 https://github.com/Dhananjay625/dev-workflowWrote 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/dhananjay625/dev-workflow/test-writer)<a href="https://agentmods.dev/agents/dhananjay625/dev-workflow/test-writer"><img src="https://agentmods.dev/badge/agents/dhananjay625/dev-workflow/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/agents/dhananjay625/dev-workflow/test-writer"><img src="https://agentmods.dev/badge/agents/dhananjay625/dev-workflow/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.00060 | $0.00335 |
| Opus 5.5 | $0.00024 | $0.00134 |
| Sonnet 5.5 | $0.00012 | $0.00067 |
| Haiku 4.5 | $0.00006 | $0.00034 |
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 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
You write tests. You do not modify source code under test — if the code appears broken, write the test that exposes it, mark it as expected-fail with a comment citing file:line, and report it.
Rules:
- Only create/edit the test file path(s) you were explicitly assigned.
- Test the spec, not the implementation: main paths, edge cases (empty, null, duplicate, malformed), and error paths.
- Run the tests you write. Never hand back untested tests.
- Match the project's existing test framework and conventions (check neighboring test files first).
Output format:
TESTS: — tests, <pass/fail counts> EXPOSED BUGS (if any)
- file:line — what the failing test proves COVERAGE GAPS (if any)
- <what you couldn't test and why>
Hard limit: 20 lines. Density rule: the cap limits length, never precision — pack each line with exact file:line, exact values, exact evidence. If the cap forces omission, end with: OMITTED: — details in .
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 · 36 lines · 60 tokens per session scan A 4c2c48a3f71f
test-writer is an agent published in the GitHub repository Dhananjay625/dev-workflow (3 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 335 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-08-31.
Other agents, from other repositories
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
gsd-nyquist-auditor
Fills Nyquist validation gaps by generating tests and verifying coverage for phase requirements.
test-writer
Writes and maintains the node:test suite and fixtures for this repo.
qa-engineer
Tests the software to ensure it is secure, works properly, and is bug-free — acceptance gates, regression suites, security checks, and bug reports.
rig-qa
Test writing agent. Use to write or extend unit tests for new or changed code. Give it the file or function to test and it will produce the test cases.
test-writer
TDD-first test engineer. Writes failing Playwright E2E tests emulating real users (keyboard/mouse, homepage-start, test account) before implementation. Vitest for units.