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/CES-Ltd/LumiWrote 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/ces-ltd/lumi/octo-tdd)<a href="https://agentmods.dev/commands/ces-ltd/lumi/octo-tdd"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-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/ces-ltd/lumi/octo-tdd"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-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.00743 |
| Opus 5 | $0.00005 | $0.00371 |
| Sonnet 5 | $0.00002 | $0.00149 |
| Haiku 4.5 | $0.00001 | $0.00074 |
Grade A, and why
octo-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 12d 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
89% identical to octo-tdd — 112 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD - Test-Driven Development Skill
Your first output line MUST be: 🐙 Octopus TDD Mode
🤖 INSTRUCTIONS FOR CLAUDE
When the user invokes this command (e.g., /octo:tdd <arguments>):
Step 1: Ask Clarifying Questions
CRITICAL: Before starting TDD, use the AskUserQuestion tool to gather context:
Ask 3 clarifying questions to ensure appropriate test strategy:
AskUserQuestion({
questions: [
{
question: "What's your test coverage goal?",
header: "Coverage",
multiSelect: false,
options: [
{label: "Critical paths only", description: "Focus on business-critical flows"},
{label: "Standard coverage ~80%", description: "Industry-standard coverage target"},
{label: "Comprehensive >90%", description: "High coverage for safety-critical code"},
{label: "Full mutation testing", description: "Maximum rigor with mutation tests"}
]
},
{
question: "What test style fits this feature?",
header: "Test Style",
multiSelect: false,
options: [
{label: "Unit tests focus", description: "Isolated component testing"},
{label: "Integration tests", description: "Module interaction testing"},
{label: "E2E tests", description: "Full user flow testing"},
{label: "Mix of all", description: "Test pyramid approach"}
]
},
{
question: "What's the complexity level of this feature?",
header: "Complexity",
multiSelect: false,
options: [
{label: "Simple CRUD", description: "Basic create/read/update/delete"},
{label: "Moderate business logic", description: "Some conditional logic and validation"},
{label: "Complex algorithms", description: "Significant computation or logic"},
{label: "Distributed systems", description: "Multiple services, async, eventual consistency"}
]
}
]
})
WAIT for the user's answers before proceeding.
After receiving answers, incorporate them into the TDD approach and test depth.
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.
- 12d ago First seen · 106 lines · 9 tokens per session scan A 036328c4473f
octo-tdd is a command published in the GitHub repository CES-Ltd/Lumi (31 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 743 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to octo-tdd, differing in 112 lines, and is treated as a copy.
Other commands, from other repositories
implement
Execute tasks from a track's implementation plan following TDD workflow.
tdd
A command for test-driven development, a method where you write a failing test first, then code to pass it, and finally improve the code.
plan-eng-review
Engineering architecture gate — lock architecture, diagrams, edge cases, and test matrix before writing implementation code.
plan-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
ralph.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
test
Test-driven development workflow using test-engineer agent.