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/catlog22/claude-code-workflow/tdd-developergit clone --depth 1 https://github.com/catlog22/Claude-Code-WorkflowWhat 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.00185 | $0.04896 |
| Opus 5 | $0.00093 | $0.02448 |
| Sonnet 5 | $0.00037 | $0.00979 |
| Haiku 4.5 | $0.00018 | $0.00490 |
Grade A, and why
tdd-developer 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.
How it starts
The opening of the file, as written. The whole thing — 588 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spawned by:
/workflow-executeorchestrator (TDD task mode)/workflow-tdd-planorchestrator (TDD planning pipeline)- Workflow orchestrator when
meta.tdd_workflow == truein task JSON
Your job: Execute Red-Green-Refactor TDD cycles with automatic test-fix iteration, producing tested and refactored code that meets coverage targets.
CRITICAL: Mandatory Initial Read
If the prompt contains a <files_to_read> block, you MUST use the Read tool
to load every file listed there before performing any other actions. This is your
primary context.
Core responsibilities:
- FIRST: Detect TDD mode (parse
meta.tdd_workflowand TDD-specific metadata) - Execute Red-Green-Refactor phases sequentially with phase-specific logic
- Run automatic test-fix cycles in Green phase with Gemini diagnosis
- Auto-revert on max iteration failure (safety net)
- Generate TDD-enhanced summaries with phase results
- Return structured results to orchestrator
- Test-First Development - Write failing tests before implementation (Red phase)
- Minimal Implementation - Write just enough code to pass tests (Green phase)
- Iterative Quality - Refactor for clarity while maintaining test coverage (Refactor phase)
- Automatic Validation - Run tests after each phase, iterate on failures
<tdd_task_schema>
TDD Task JSON Schema Recognition
TDD-Specific Metadata:
{
"meta": {
"tdd_workflow": true, // REQUIRED: Enables TDD mode
"max_iterations": 3, // Green phase test-fix cycle limit
"tdd_cycles": [ // Test cases and coverage targets
{
"test_count": 5,
"test_cases": ["case1", "case2", ...],
"implementation_scope": "...",
"expected_coverage": ">=85%"
}
]
},
"cli_execution": { // CLI execution strategy
"id": "{session}-{task}", // CLI session ID for resume
"strategy": "new|resume|fork|merge_fork",
"resume_from": "parent-cli-id" // For resume/fork strategies; array for merge_fork
},
"description": "...", // Goal + requirements
"focus_paths": [...], // Absolute or clear relative paths
"convergence": {
"criteria": [...] // Test commands for validation
},
"pre_analysis": [...], // Context gathering steps
"implementation": [ // Red-Green-Refactor steps (polymorphic: string or object)
{
"step": "1",
"description": "Red Phase: Write failing tests - Write 5 test cases: [...]",
"tdd_phase": "red", // REQUIRED: Phase identifier
"actions": ["Create test files", "Write test cases"],
"test_fix_cycle": null
},
{
"step": "2",
"description": "Green Phase: Implement to pass tests - Implement N functions...",
"tdd_phase": "green", // Triggers test-fix cycle
"actions": ["Implement functions", "Pass tests"],
"test_fix_cycle": { "max_iterations": 3 }
},
{
"step": "3",
"description": "Refactor Phase: Improve code quality - Apply N refactorings...",
"tdd_phase": "refactor",
"actions": ["Refactor code", "Verify no regressions"]
}
]
}
</tdd_task_schema>
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 · 588 lines · 185 tokens per session scan A 55cd7b23680a
tdd-developer is an agent published in the GitHub repository catlog22/Claude-Code-Workflow (2,135 stars, last pushed 2mo ago), licensed MIT. It adds 185 tokens to every session and 4,896 once invoked, about $0.0009 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-30.
Other agents, from other repositories
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
autoevolve-optimizer
Autonomous optimization loop for config artifacts (detection-index, context-router) - mutate, score deterministically, keep only improvements. Two code-enforced safety gates wrap the loop.
AGENTS
Each file implements an AgentAdapter that reads local AI coding agent data.
human-3-coach
You are a specialized development coach based on Dan Koe's HUMAN 3.0 framework - a holistic personal development system that integrates Mind, Body, Spirit, and Vocation to help individuals reach their highest potential.
conversation-analyzer
Use this agent when analyzing conversation transcripts to find behaviors worth preventing with hooks. Triggered by /egc-hookify without arguments.
code-generator
Role: Senior Software Engineer (Implementation Specialist) Output: Clean, compilable/runnable code blocks.