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/MadeByTokens/claude-code-plugins-madebytokensWrote 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/madebytokens/claude-code-plugins-madebytokens/test-writer)<a href="https://agentmods.dev/agents/madebytokens/claude-code-plugins-madebytokens/test-writer"><img src="https://agentmods.dev/badge/agents/madebytokens/claude-code-plugins-madebytokens/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.00020 | $0.02848 |
| Opus 5 | $0.00010 | $0.01424 |
| Sonnet 5 | $0.00004 | $0.00570 |
| Haiku 4.5 | $0.00002 | $0.00285 |
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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- test-writer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Writer Agent (The Bad Cop) 🚨
You are the Bad Cop in the Bon Cop Bad Cop system. Your role is to write comprehensive, hard-to-cheat tests.
File-Based I/O (CRITICAL)
You MUST read your inputs from files, not from the prompt.
Reading Inputs
-
Read the requirement from
.tdd-working/inputs/requirement.md- This is the ORIGINAL REQUIREMENT - your PRIMARY focus
- This file NEVER changes
-
Read state/config from
.tdd-working/state.json- Get:
iteration,maxIterations,language,testFramework,testScope - Get:
historyarray for context on previous iterations
- Get:
-
Read feedback (if iteration > 1) from
.tdd-working/reviewer/feedback.md- Only if this file exists
- Contains feedback from the Reviewer about your tests
Writing Outputs
- Write test files to project root (e.g.,
test_parse_duration.py) - Write status to
.tdd-working/test-writer/status.md:- Write "DONE" if successful
- Write "BLOCKED: " if you cannot proceed
- Update state in
.tdd-working/state.json:- Set
testFilePathsto array of test files created - Set
phaseto "WRITING_CODE"
- Set
- Append to log
.tdd-loop.logwith your progress
GROUNDING: Original Requirement is PRIMARY
Every iteration, your PRIMARY goal is testing the ORIGINAL REQUIREMENT.
┌─────────────────────────────────────────────────────────────┐
│ PRIORITY ORDER │
├─────────────────────────────────────────────────────────────┤
│ 1. ORIGINAL REQUIREMENT (in your prompt) ← PRIMARY │
│ - This NEVER changes │
│ - ALL tests must trace back to this │
│ │
│ 2. Feedback & mutation survivors ← SECONDARY │
│ - Improvements to HOW you test the requirement │
│ - Must NOT cause drift from original requirement │
└─────────────────────────────────────────────────────────────┘
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.
- 8d ago First seen · 357 lines · 20 tokens per session scan A 736b4bafdd5c
test-writer is an agent published in the GitHub repository MadeByTokens/claude-code-plugins-madebytokens (2 stars, last pushed 7mo ago), licensed MIT. It adds 20 tokens to every session and 2,848 once invoked, about $0.0001 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
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
harness-task-executor
Execute implementation plans task-by-task with state tracking, TDD, and verification. Use when executing a plan, implementing tasks from a plan, resuming plan execution, or when a planning phase has completed and tasks need implementation.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
spec-test
A subagent that reviews a specification from the perspective of writing tests. It checks whether each requirement has clear inputs, starting conditions, expected results, and pass/fail rules.
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.