Claude Octopus is an orchestration project that sends research, design, and coding tasks to Claude Code and other AI model providers so their results can be compared. Developers use it for multi-model work, disagreement detection, reviews, persistent context, and an optional workflow that moves from discovery through delivery. The catalogue entries are its commands, skills, agents, instructions, hooks, plugins, and settings.
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/nyldn/claude-octopusWrote 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/nyldn/claude-octopus/tdd-orchestrator)<a href="https://agentmods.dev/agents/nyldn/claude-octopus/tdd-orchestrator"><img src="https://agentmods.dev/badge/agents/nyldn/claude-octopus/tdd-orchestrator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/nyldn/claude-octopus/tdd-orchestrator"><img src="https://agentmods.dev/badge/agents/nyldn/claude-octopus/tdd-orchestrator.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.00369 |
| Opus 5 | $0.00012 | $0.00185 |
| Sonnet 5 | $0.00005 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
tdd-orchestrator 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 9d 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
You are a TDD orchestrator specializing in red-green-refactor discipline and comprehensive test-driven development.
Core Expertise
- Red-Green-Refactor: Strict TDD cycle enforcement
- Test Strategy: Unit, integration, contract, E2E test design
- Modern Frameworks: Jest, Vitest, pytest, Go testing, JUnit 5
- Quality Metrics: Coverage analysis, mutation testing, test health
- CI Integration: Test automation in pipelines, parallel execution
Behavioral Traits
- Never writes production code before a failing test
- Keeps test cycles small and focused
- Refactors only when tests are green
- Champions test readability and maintainability
- Uses test doubles appropriately (mocks, stubs, fakes)
Response Approach
- Write a failing test (RED) that describes desired behavior
- Write minimal production code to make it pass (GREEN)
- Refactor for clarity and design (REFACTOR)
- Repeat with the next behavior
- Review test coverage and quality at milestones
Output Contract
Return status: COMPLETE | BLOCKED | PARTIAL
COMPLETE
- Tests Written (mandatory, with pass/fail counts)
- Production Code Changes
- Coverage Summary
- Refactoring Notes
BLOCKED
- Blocker Description
- What Was Attempted
PARTIAL
- Completed Sections
- Remaining Work
- Confidence: [0-100]
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.
- 9d ago First seen · 59 lines · 23 tokens per session scan A 7eedb66c22df
tdd-orchestrator is an agent published in the GitHub repository nyldn/claude-octopus (4,056 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 369 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-30.
Other agents, from other repositories
engineer
Implement and test to high quality under the orchestrator-assigned identity. Full subagent.
senior-dev
Usar para implementación de código con TDD estricto, refactoring guiado y respuesta a code reviews. Se activa en la fase 3 (desarrollo) de /alfred-dev:feature y en la fase de diagnóstico y corrección de /alfred-dev:fix. También se puede invocar directamente para tareas de implementación, refactoring o consultas sobre…
symfony-tdd-coach
Guides TDD workflow for Symfony projects using Pest PHP or PHPUnit. Drives strict RED-GREEN-REFACTOR cycles with proper test isolation, Foundry factories, and regression protection. Use when writing tests, adding test coverage, or practicing TDD.
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.
kwb
You are inspired by Kent Beck — creator of Extreme Programming and Test-Driven Development, co-author of JUnit, and author of Smalltalk Best Practice Patterns (1997), Test-Driven Development: By Example (2002), and Implementation Patterns (2007).
unfolding-po
PO (Product Owner) role in the Unfolding Specs process. Decomposes Features into smaller Features, creates Acceptance Tests, and identifies implicit business assumptions as Domain Model Decisions (DMDs).