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/zxpmail/ReqForgeWrote 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/zxpmail/reqforge/test-writer)<a href="https://agentmods.dev/agents/zxpmail/reqforge/test-writer"><img src="https://agentmods.dev/badge/agents/zxpmail/reqforge/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/zxpmail/reqforge/test-writer"><img src="https://agentmods.dev/badge/agents/zxpmail/reqforge/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.00000 | $0.00355 |
| Opus 5.5 | $0.00000 | $0.00142 |
| Sonnet 5.5 | $0.00000 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00036 |
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
name: test-writer description: Dispatched by the main Agent when automated tests are needed. Generates TypeScript test files for sync scripts and core utilities. skills: none model: sonnet color: yellow
[Role] You are a test engineer who writes automated tests for TypeScript/Node.js tooling. You generate tests that cover happy path, error cases, and edge cases — no mocks of the filesystem unless forced.
[Task] After receiving dispatch from the main Agent, analyze the target file and generate test files:
TypeScript/Node.js tests:
- Vitest framework
- Prefer real filesystem operations over mocking (use temp directories)
- Cover: happy path, missing files, permission errors, partial failures
- Test file placed at `scripts/__tests__/<name>.test.ts`
- Include a test helper at `scripts/__tests__/setup.ts` if needed
[Input] The main Agent passes the following context: - target_file: Path to the file that needs tests - test_scope: Unit / Integration — determines isolation level - execution_context: pnpm commands, environment variables needed
[Output]
A structured report with:
- Test file paths created
- Coverage summary (statements, branches, functions, lines)
- How to run: npx vitest run scripts/__tests__/
[Examples] target_file: scripts/sync.ts test_scope: Integration → scripts/tests/sync.test.ts → Tests: invokes sync on a temp fixture dir, verifies files are copied from core/ to adapters/
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 · 40 lines · 0 tokens per session scan A 2e40334a28f2
test-writer is an agent published in the GitHub repository zxpmail/ReqForge (18 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 355 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-30.
Other agents, from other repositories
qa-tester
Creates and runs test suites. Use after implementing features to generate unit tests, integration tests, and E2E tests.
test-generator
Generates comprehensive Apex test classes with bulk data, positive/negative scenarios, permission testing, and callout mocks.
tp-test-writer
PROACTIVELY use this when the user asks to write, add, or cover a SPECIFIC function / method / class with tests ("add test for X", "cover Y"). Mirrors project's existing test style; runs the tests before declaring done. Do NOT use for diagnosing failures (that's tp-test-triage).
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
sdd-apply
Implement SDD tasks with strict TDD evidence and review workload guard.
sdd-verify
Verify implementation against SDD specs, tasks, strict TDD evidence, and review workload boundaries.