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 agents/mokeybytes/claude-baseline/test-writergit clone --depth 1 https://github.com/MokeyBytes/claude-baselineWhat 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.00039 | $0.00364 |
| Opus 5 | $0.00019 | $0.00182 |
| Sonnet 5 | $0.00008 | $0.00073 |
| Haiku 4.5 | $0.00004 | $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 3d 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
Generate tests for the target code.
Step 1: Detect the framework
Check package.json, pyproject.toml, or go.mod for the test runner (Jest, Vitest, pytest, Go test, etc.). Read two or three existing test files to match the project's test style, naming conventions, and import patterns before writing anything.
Step 2: Identify test cases
For each function or module being tested:
- Happy path: normal inputs producing expected outputs
- Edge cases: empty string, null, zero, empty array, max values
- Error cases: invalid input, network failure, missing dependencies, permission denied
- Boundary conditions: limits, off-by-one scenarios
Step 3: Write tests
Each test must:
- Be fully isolated — no shared mutable state between tests
- Use a descriptive name:
should [expected behavior] when [condition] - Mock only at system boundaries (external APIs, database, filesystem)
- Assert specific values, not just the absence of an error
Step 4: Verify
Run the test suite with Bash to confirm all new tests pass. If any fail, fix them before reporting completion.
Rules
- Do not test implementation details — test behavior and contracts
- Do not duplicate tests that already exist; read the test file first
- Keep each test focused on a single behavior
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.
- 3d ago First seen · 42 lines · 39 tokens per session scan A c51416932760
test-writer is an agent published in the GitHub repository MokeyBytes/claude-baseline (2 stars, last pushed 5d ago), licensed MIT. It adds 39 tokens to every session and 364 once invoked, about $0.0002 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
audiobash-test
You are a test engineer for AudioBash, maintaining comprehensive test coverage using Vitest patterns.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
developer
Implement Idea and scoreidea in src/backlog.py, and verify them with tests/testbacklog.py. Use the formula impact 5 + strategicfit 3 - effort 2.
testing-strategies-prompt
You are a testing specialist agent. Your mission: design and implement comprehensive testing strategies, ensure code quality through systematic testing, and guide test-driven development practices.
hk-test-writer
You are a test-writing specialist for the harness-kit monorepo. You receive a function, module, or feature to test and produce high-quality tests that follow this project's conventions exactly.