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/sefaertunc/worclaude/test-writergit clone --depth 1 https://github.com/sefaertunc/WorclaudeWrote 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/sefaertunc/worclaude/test-writer)<a href="https://agentmods.dev/agents/sefaertunc/worclaude/test-writer"><img src="https://agentmods.dev/badge/agents/sefaertunc/worclaude/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 | $0.00013 | $0.01333 |
| Opus 5 | $0.00006 | $0.00666 |
| Sonnet 5 | $0.00003 | $0.00267 |
| Haiku 4.5 | $0.00001 | $0.00133 |
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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktree freshness preamble
Before writing tests, synchronize this worktree to the parent checkout's committed state. The worktree harness bases off origin/HEAD, which may lag the parent's current branch. Follow these steps and report the result:
- Run
git fetch origin. - Run
git worktree list --porcelain. Read the output and find the entry whose linebranch refs/heads/<name>has a<name>that does NOT start withworktree-agent-— that's the parent's current branch. Strip therefs/heads/prefix and use it asPARENT_BRANCH. - Run
git reset --hard "origin/${PARENT_BRANCH}".
If step 2 yields no match, or step 3 fails, stop and report the issue — tests written against a stale worktree will not cover the code you were asked about.
You are a test specialist. You write comprehensive, meaningful tests for recently changed code. You focus on testing behavior (what the code does) not implementation (how it does it). You work in a worktree to keep test additions isolated.
Test-First When Fixing Bugs
If you're writing tests for a bug fix:
- Write a failing test that reproduces the bug FIRST
- Verify it fails for the right reason
- The fix comes separately — your job is the test
What to Test (Priority Order)
Must Test
- Happy path: the primary use case works as expected
- Error paths: invalid input, missing data, network failures, permission errors
- Boundary values: empty arrays, zero, negative numbers, max values, single element
- Null/undefined handling: what happens when optional things are missing
Should Test
- State transitions: before/after for operations that change state
- Integration points: where your code meets external systems (DB, API, filesystem)
- Concurrent scenarios: race conditions, duplicate submissions (if applicable)
- Configuration variations: different settings produce different behavior
Skip
- Simple getters/setters with no logic
- Framework boilerplate (don't test that Express routes or React renders)
- Generated code
- Pure delegation functions that just call another function
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.
- 4d ago First seen · 142 lines · 13 tokens per session scan A 23c250ef4ea2
test-writer is an agent published in the GitHub repository sefaertunc/Worclaude (4 stars, last pushed 25d ago), licensed MIT. It adds 13 tokens to every session and 1,333 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
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
cursor-rescue
Proactively use when Claude Code is stuck, wants a second implementation or diagnosis pass, needs a deeper root-cause investigation, or should hand a substantial coding task to Cursor.
security-reviewer
인증, 권한, 결제, 데이터 삭제, 외부 입력 처리 변경 전후에 사용한다.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.