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/commands/nyldn/claude-octopus/tdd)<a href="https://agentmods.dev/commands/nyldn/claude-octopus/tdd"><img src="https://agentmods.dev/badge/commands/nyldn/claude-octopus/tdd/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/commands/nyldn/claude-octopus/tdd"><img src="https://agentmods.dev/badge/commands/nyldn/claude-octopus/tdd.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.00009 | $0.00660 |
| Opus 5.5 | $0.00004 | $0.00264 |
| Sonnet 5.5 | $0.00002 | $0.00132 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
tdd 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 1mo 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.
This is a copy
95% identical to octo-tdd — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Octopus TDD
Load skills/blocks/engineering-method-selection.md from the installed plugin
and apply only the methods relevant to this task. Preserve this entry point's
execution contract and output format. Read referenced skills as instructions;
do not invoke the current command recursively or add provider calls from a seat.
Load and follow
${HOME}/.claude-octopus/plugin/.claude/skills/skill-tdd/SKILL.md.
Treat --peer-review as an instruction to request one bounded independent test
design review through existing Octopus routing. Do not pass the token or the
remaining user text into a shell command. Natural-language independent-review
requests have the same meaning. Otherwise run on the current host with zero
additional provider dispatches unless an existing escalation policy both
requires and permits review under the effective preferences and billing limits.
Risk alone does not authorize a paid call; honor explicit host-only requests.
Step 1: Ask Clarifying Questions when needed
Do not interrupt a well-specified task. If the repository and request leave a
material choice unresolved, use AskUserQuestion for only the unanswered items
from this intake:
AskUserQuestion({
questions: [
{
question: "Which coverage boundary should prove the observable behavior?",
header: "Coverage",
multiSelect: false,
options: [
{label: "Public API", description: "Prove behavior at the caller-facing API."},
{label: "Integration", description: "Prove behavior across component boundaries."},
{label: "User flow", description: "Prove the complete user-visible path."}
]
},
{
question: "Which test style should carry the regression?",
header: "Test style",
multiSelect: false,
options: [
{label: "Unit", description: "Use the narrowest stable public boundary."},
{label: "Integration", description: "Exercise the real collaborating components."},
{label: "End to end", description: "Exercise the supported runtime path."}
]
},
{
question: "What complexity and risk level does this change carry?",
header: "Complexity",
multiSelect: false,
options: [
{label: "Focused", description: "Run the focused test and directly affected suite."},
{label: "Standard", description: "Add the repository's normal changed-file gates."},
{label: "High risk", description: "Add integration, race, or security coverage."}
]
}
]
})
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.
- 1mo ago Changed · -31 lines 3c60d36a2c3e
- 1mo ago First seen · 108 lines · 9 tokens per session scan A 215a5afc7feb
tdd is a command published in the GitHub repository nyldn/claude-octopus (4,332 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 660 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to octo-tdd, differing in 3 lines, and is treated as a copy.
Other commands, from other repositories
api-aqa-flow
Workflow for backend API test automation: TMS / Issue Tracker test cases → automated API tests, HITL-gated.
atdd
Start the ATDD workflow for a new feature. Optionally provide a feature description as an argument.
debug
Systematic root-cause investigation, then fix with TDD — never proposes a fix before finding the cause; resumable diagnosis + regression test in .orc/ state. Workspace-aware. For a quick one-off look without session state, prefer the bundled /debug.
partition-dev
Derive test cases from Z specification using TTF testing tactics.
ccc-feature-start
Kick off a feature: research context, create an isolated branch, confirm a green baseline, write a task breakdown, and the first failing test. Use when starting new feature work in a git repository.
loop
Autonomous execution loop. Runs the TDD cycle repeatedly until all tasks in an epic are complete, with circuit breaker protection and PR workflow.