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
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add nyldn/claude-octopus/plugin install octoWrote 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/skills/nyldn/claude-octopus/skill-council)<a href="https://agentmods.dev/skills/nyldn/claude-octopus/skill-council"><img src="https://agentmods.dev/badge/skills/nyldn/claude-octopus/skill-council/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/skills/nyldn/claude-octopus/skill-council"><img src="https://agentmods.dev/badge/skills/nyldn/claude-octopus/skill-council.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.00030 | $0.01709 |
| Opus 5 | $0.00015 | $0.00855 |
| Sonnet 5 | $0.00006 | $0.00342 |
| Haiku 4.5 | $0.00003 | $0.00171 |
Grade A, and why
skill-council 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Council
Use this skill for /octo:council and council-style requests.
EXECUTION CONTRACT: MANDATORY
/octo:council is a runner-backed workflow. Execute the real shell runner by default:
"${CLAUDE_PLUGIN_ROOT:-$HOME/.claude-octopus/plugin}/scripts/orchestrate.sh" council <user arguments>
Sandbox-safe invocation (required under Claude Code's sandbox). orchestrate.sh
must be the FIRST token of the command. The sandbox's unsandboxed-command allowlist is a
leading-anchored prefix match, so a command that begins with cd …, an inline
VAR=… env-assignment, or any other prefix will NOT match an …/orchestrate.sh *
entry — the runner then executes sandboxed and its codex/agy seat children fail to
write temp files (Operation not permitted, agy mkstemp in /var/folders), so the
council abandons the runner and falls back to direct single-provider dispatch. To run
against a worktree, pass --dir <path> (the runner already honors -d/--dir) instead
of wrapping in cd <path> && …; set any environment in a separate prior step or via a
leading env VAR=… /abs/path/orchestrate.sh council … so the resolvable binary path is
still first. Never prefix the runner with cd.
Do not simulate a council, role-play all members inside the current model, or answer directly in place of the runner. A single-model simulation must be explicitly requested with --simulate or --single-model; when used, label the output as single-model simulation and keep the generated summary.json path visible. Otherwise, missing provider quorum is a partial/failed council, not permission to silently downgrade.
Phase 0A: Interactive Clarification
If the user invokes /octo:council with an ambiguous task, missing goal/depth intent, uncertain implementation permission, or unclear research/corpus expectations, use AskUserQuestion before running the council runner. If the prompt already includes clear flags and a clear task, skip this phase and execute immediately.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 133 lines · 30 tokens per session scan A c43d73f8dd87
skill-council is a skill published in the GitHub repository nyldn/claude-octopus (4,058 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 1,709 once invoked, about $0.0002 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-05.
Other skills, from other repositories
ai-context
Generates, updates, and audits AGENTS-first AI IDE context files. Builds canonical AGENTS.md plus thin bridges for Claude Code, Cursor (modern .cursor/rules/.mdc), Copilot, Cline (.clinerules/ directory), Windsurf, Gemini CLI, Codex CLI, and OpenCode. Use for creating, regenerating, fixing, or promoting context files…
architecture
This skill should be used when managing Architecture Decision Records or C4 diagrams.
linear-fetch
This skill should be used when a user input contains a Linear issue reference (e.g., SOL-39 or linear.app/.../issue/ ) and the downstream agent needs the screenshots embedded in the issue as visual context.
invoice
This skill should be used when the founder wants to get paid through their own Stripe account: list who owes them, create and send an invoice behind a human-approval preview, or chase an overdue one. Test-mode only in v1.
kb-search
This skill should be used when searching the knowledge base for files matching keywords or YAML frontmatter facets (tag, category) across domains.
legal-generate
This skill should be used when generating draft legal documents for a project or company. It gathers company context interactively, invokes the legal-document-generator agent, and writes markdown output.