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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/nyldn/claude-octopusnpx agentmods add skills/nyldn/claude-octopus/skill-statusWrote 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-status)<a href="https://agentmods.dev/skills/nyldn/claude-octopus/skill-status"><img src="https://agentmods.dev/badge/skills/nyldn/claude-octopus/skill-status/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-status"><img src="https://agentmods.dev/badge/skills/nyldn/claude-octopus/skill-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 331 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00022 | $0.03051 |
| Opus 5 | $0.00011 | $0.01525 |
| Sonnet 5 | $0.00004 | $0.00610 |
| Haiku 4.5 | $0.00002 | $0.00305 |
Grade A, and why
skill-status 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 7d 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 — 504 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Status Dashboard
Overview
Display current project status, roadmap progress, blockers, and intelligent next-action suggestions based on workflow state.
Core principle: Read state → Display dashboard → Route intelligently.
When to Use
Use this skill when user asks:
- "What's the status?" or "Show me progress"
- "Where am I in the workflow?"
- "What should I do next?"
- "What's the current phase?"
- "Are there any blockers?"
- "What have I been working on?" or "Summarize recent work"
- "Update project memory" or "Update CLAUDE.md"
Do NOT use for:
- Creating new projects (use /octo:embrace)
- Modifying state (use octo-state.sh write_state)
- Detailed phase planning (use flow-* skills)
The Process
Phase 1: Check Project Initialization
Step 1: Verify .octo/ Directory Exists
# Check if project is initialized
if [[ ! -d ".octo" ]]; then
echo "No project initialized"
exit 1
fi
If .octo/ does not exist:
## Project Status
**Status:** Not initialized
No Claude Octopus project found in this directory.
### Get Started
Run `/octo:embrace [your project description]` to initialize a new project and start the Double Diamond workflow.
**Example:**
/octo:embrace build a user authentication system
This will:
1. Create .octo/ directory structure
2. Initialize STATE.md, PROJECT.md, ROADMAP.md
3. Begin Discover phase (research and exploration)
Stop here - do not proceed to Phase 2.
Phase 2: Read Current State
Step 1: Execute octo-state.sh read_state
# Read current state from STATE.md
./scripts/octo-state.sh read_state
Expected output format:
schema=1.0
last_updated=2026-02-02T10:30:00Z
current_phase=2
current_position=define-requirements
status=in_progress
Step 2: Parse State Variables
Extract key-value pairs:
current_phase- Phase number (1-4)current_position- Specific position within phasestatus- Current workflow statuslast_updated- Last state modification timestamp
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.
- 7d ago First seen · 504 lines · 22 tokens per session scan A e3e9003e5b10
skill-status is a skill published in the GitHub repository nyldn/claude-octopus (4,056 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 3,051 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-02.
Other skills, from other repositories
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.
drain-labeled-backlog
This skill should be used when draining a labeled issue backlog (deferred-scope-out, code-review, type/security) in one cleanup PR. Groups by code area and delegates to /soleur:one-shot.
cpo
Orchestrates the product domain -- assesses product strategy, validates business models, and delegates to specialist agents (spec-flow-analyzer, ux-design-lead, business-validator, competitive-intelligence). Use individual product agents for focused tasks; use this agent for cross-cutting product strategy and…
file-todos
This skill should be used when managing the file-based todo tracking system in the todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with code review.
campaign-calendar
This skill should be used when generating or refreshing the rolling campaign calendar. Scans knowledge-base/marketing/distribution-content/ markdown frontmatter, groups by status (overdue/upcoming/draft/published), writes a calendar view.
coo
Orchestrates the operations domain -- assesses operational posture, recommends actions, and delegates to specialist agents (ops-advisor, ops-research, ops-provisioner). Use individual operations agents for focused tasks; use this agent for cross-cutting operations strategy and multi-agent coordination. Use cfo for…