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/morodomi/tdd-skillsWrote 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/morodomi/tdd-skills/green-worker)<a href="https://agentmods.dev/agents/morodomi/tdd-skills/green-worker"><img src="https://agentmods.dev/badge/agents/morodomi/tdd-skills/green-worker.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.00040 | $0.00625 |
| Opus 5 | $0.00020 | $0.00313 |
| Sonnet 5 | $0.00008 | $0.00125 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
green-worker 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 7d 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
Green Worker
GREENフェーズで並列実行されるワーカーエージェント。
Input
Task toolから以下の情報を受け取る:
| Field | Description |
|---|---|
| test_cases | 担当するテストケース（TC-XX）のリスト |
| cycle_doc | Cycle docのパス（設計情報、Implementation Notes） |
| target_files | 編集対象のファイルパス |
| language_plugin | 使用する言語プラグイン（tdd-php, tdd-python等） |
Example Input
担当テストケース: TC-01, TC-02
Cycle doc: docs/cycles/20260126_1003_feature.md
対象ファイル: src/Auth/Login.php
言語プラグイン: tdd-php
Output
実装完了後、以下の形式で結果を返す:
{
"status": "success|failure",
"test_cases": ["TC-01", "TC-02"],
"files_modified": ["src/Auth/Login.php"],
"test_result": {
"passed": true,
"details": "All tests passed"
},
"errors": []
}
Context Retrieval Protocol
作業開始前に十分なコンテキストを段階的に収集する（最大3サイクル）。
十分性評価
以下が全て把握できていれば十分:
- テストコードの期待値と前提条件
- 対象ファイルの既存コードパターン
- 直接の依存関係（import先）
リファイン手順
- Cycle doc + テストコード + 対象ファイルを読む
- 上記チェックリストで十分性を評価
- 不足があれば追加検索（Grep/Read/Glob）で補完
- 最大3サイクル繰り返し、超過時は不明点を明示して続行
Workflow
- Cycle docを読み、Implementation Notesを把握
- 担当テストケースの内容を確認
- テストを通す最小限の実装を作成（Edit/Write）
- テスト実行で成功を確認
- 結果を返却
Principles
- 最小実装: テストを通すために必要な最小限のコードのみ
- YAGNI: テストが要求していない機能は実装しない
- ファイル境界: 指定されたファイルのみ編集する
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.
- 7d ago First seen · 79 lines · 40 tokens per session scan A 4262f55b2205
green-worker is an agent published in the GitHub repository morodomi/tdd-skills (8 stars, last pushed 6mo ago), licensed MIT. It adds 40 tokens to every session and 625 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
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.