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/octo-retro)<a href="https://agentmods.dev/commands/nyldn/claude-octopus/octo-retro"><img src="https://agentmods.dev/badge/commands/nyldn/claude-octopus/octo-retro/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/octo-retro"><img src="https://agentmods.dev/badge/commands/nyldn/claude-octopus/octo-retro.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.00015 | $0.01471 |
| Opus 5 | $0.00008 | $0.00736 |
| Sonnet 5 | $0.00003 | $0.00294 |
| Haiku 4.5 | $0.00002 | $0.00147 |
Grade A, and why
octo-retro 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 8d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- retro — 95% identical, 3 lines differ
- octo-retro — 88% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retro — Engineering Retrospective from Git History
Your first output line MUST be: 🐙 Octopus Retrospective
Generate data-driven engineering retrospectives by mining git history. Surfaces commit patterns, contributor breakdown, hotspots, session analysis, and AI-assisted commit tracking.
Usage
/octo:retro # Last 7 days (default)
/octo:retro 24h # Last 24 hours
/octo:retro 14d # Last 14 days
/octo:retro 30d # Last 30 days
Instructions
When the user invokes /octo:retro, you MUST follow these steps exactly.
1. Parse Time Window
Accept an optional argument for the time window. Default to 7d if none provided.
Supported formats:
24h— last 24 hours (--since='24 hours ago')7d— last 7 days (--since='7 days ago')14d— last 14 days (--since='14 days ago')30d— last 30 days (--since='30 days ago')
Map the argument to a git --since value. If the argument does not match a supported format, warn the user and fall back to 7d.
2. Gather Git Data
Run the following git commands to collect raw data. Each command MUST be executed — do NOT skip any.
Commit list:
git log --oneline --since='<window>' --no-merges
LOC changes (lines added/removed per file):
git log --numstat --since='<window>' --no-merges --format=''
Contributor leaderboard:
git shortlog -sn --since='<window>' --no-merges
Hotspot analysis (files modified most often):
git log --format='' --name-only --since='<window>' --no-merges | sort | uniq -c | sort -rn | head -20
PR merge count (merge commits):
git log --oneline --since='<window>' --merges | wc -l
Commit timestamps for session detection:
git log --format='%at %H %s' --since='<window>' --no-merges
AI-assisted commit detection:
git log --since='<window>' --no-merges --format='%b' | grep -ci 'Co-Authored-By:'
Current user identification:
git config user.name
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.
- 8d ago First seen · 208 lines · 15 tokens per session scan A 7c450e479f61
octo-retro is a command published in the GitHub repository nyldn/claude-octopus (4,061 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 1,471 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-09-03.
Other commands, from other repositories
replay
You are reconstructing the historical evolution of this sprint by recompiling every version of claims.json from git history.
apex-git-commit
Stage everything except agent-output/, infra/, and .github/skills/sensei/ (unless on feat/skills-sensei), auto-generate a conventional commit, push, then prompt to open or update a PR. CLI-only (git + gh).
genshijin-commit
A command that writes a commit message for changes already placed in Git's staging area. It follows the repository's existing language and uses a short imperative subject without AI attribution.
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
explain
/explain Explain the last agent action (quick mode) /explain --verbose Full trace with file changes and decision rationale /explain --story STORY-XXX All actions for a story in chronological order /explain --agent Last action by a specific agent /explain --session All actions from a specific session /explain --diff…
flow
Universal workflow entry point. Use /flow for skill-driven GitHub development. Verbs: start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue.