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-careful)<a href="https://agentmods.dev/commands/nyldn/claude-octopus/octo-careful"><img src="https://agentmods.dev/badge/commands/nyldn/claude-octopus/octo-careful/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-careful"><img src="https://agentmods.dev/badge/commands/nyldn/claude-octopus/octo-careful.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.00010 | $0.00450 |
| Opus 5 | $0.00005 | $0.00225 |
| Sonnet 5 | $0.00002 | $0.00090 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade C, and why
octo-careful scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- `rm -rf` (except safe targets: node_modules, dist, .next, __pycache__, build, coverage, .turbo) Copies of this mod
2 near-identical copies found in the catalogue:
- careful — 94% identical, 3 lines differ
- octo-careful — 91% identical, 13 lines differ
What it actually says
Careful Mode - Destructive Command Warnings
Instructions
When the user invokes /octo:careful, activate careful mode for the current session.
Activation
Write the activation state file:
_OCTO_SESSION_ID="${CLAUDE_CODE_SESSION_ID:-${CLAUDE_SESSION_ID:-$$}}"
echo "active" > "/tmp/octopus-careful-${_OCTO_SESSION_ID}.txt"
What It Does
Careful mode adds a PreToolUse safety net on Bash commands. Before any destructive command executes, you will be prompted to confirm. This catches accidental damage without blocking normal work.
Detected patterns:
rm -rf(except safe targets: node_modules, dist, .next, pycache, build, coverage, .turbo)DROP TABLE,DROP DATABASE,TRUNCATEgit push --force,git push -fgit reset --hardgit checkout .,git restore .kubectl deletedocker rm -f,docker system prune
Deactivation
Remove the state file to deactivate:
_OCTO_SESSION_ID="${CLAUDE_CODE_SESSION_ID:-${CLAUDE_SESSION_ID:-$$}}"
rm -f "/tmp/octopus-careful-${_OCTO_SESSION_ID}.txt"
Usage
/octo:careful
After activation, confirm to the user:
⚠️ Careful mode activated. Destructive commands will now require confirmation before executing.
When to Use
- Working in production environments
- Unfamiliar codebases where accidental deletion is risky
- Pair programming sessions where extra safety is desired
- Any time you want a safety net against destructive commands
See Also
/octo:freeze— Restrict edits to a specific directory/octo:guard— Activate both careful + freeze together/octo:unfreeze— Remove freeze restriction
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 · 67 lines · 10 tokens per session scan C 7835f7812903
octo-careful is a command published in the GitHub repository nyldn/claude-octopus (4,061 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 450 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
ai-context
Generate, update, or audit AI IDE context files with AGENTS.md as the canonical shared context and tool-specific bridge files. Signal Gate principle — only what agents cannot discover: $ARGUMENTS.
sync
Analyze codebase and populate knowledge-base with conventions, patterns, and technical debt.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.