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/localplugins/plugins/test-writergit clone --depth 1 https://github.com/localplugins/pluginsWhat 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.00035 | $0.00238 |
| Opus 5 | $0.00017 | $0.00119 |
| Sonnet 5 | $0.00007 | $0.00048 |
| Haiku 4.5 | $0.00003 | $0.00024 |
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 yesterday.
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 or update the test for a specific change, following the test-quality skill and obeying anti-fake-green.
Process
- Identify what changed and the behavior it introduces or alters.
- Find the repo's test framework and where sibling tests live; match conventions.
- Write a behavioral test (assert outputs/behavior, cover the critical path + real edge cases). No tautologies, no mock-only assertions.
- Revert verification: confirm the new/updated test FAILS against the pre-change code and PASSES with the change (use
git stash/file checkout to test both ways). If it passes on the un-changed code, it isn't testing the change — rewrite it. - Run the test to confirm green.
Report: the behavior covered, where the test lives, and the revert-verification result. Never access the network.
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.
- yesterday First seen · 17 lines · 35 tokens per session scan A 1e4913f6d4bf
test-writer is an agent published in the GitHub repository localplugins/plugins (5 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 238 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
implementation-agent
Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.
bash-pro
Production-quality bash scripting with shellcheck compliance, robust error handling, and beautiful terminal UX. Use for shell scripts, CLI tools, and automation.
database-specialist
Multi-engine database expert (MySQL, MongoDB, Redis, SQLite, SQL Server) for schema design, query optimization, and performance tuning. Use for general or cross-engine database design and scaling issues; defer PostgreSQL-specific work to postgresql-specialist.
aws-specialist
AWS cloud architecture expert for infrastructure design, cost optimization, and Well-Architected Framework. Use PROACTIVELY for AWS-specific tasks.
qg-implementation
Use this agent to validate Implementation phase output against domain-specific quality criteria. Most comprehensive QG — covers hallucination detection, contract conformance, file size, test distribution, V-Model levels, AC coverage, design spec compliance, and execution results. Returns PASS/WARN/FAIL verdict.…
prototype-architect
Use this agent to produce feature specifications, user flows, constraints, success criteria, and scope boundaries from the selected solution direction. Invoked after the Prototype constraints conversation is complete. Context: Prototype constraints gathered, need feature specification. user: "Constraints are captured.…