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/scheduler)<a href="https://agentmods.dev/commands/nyldn/claude-octopus/scheduler"><img src="https://agentmods.dev/badge/commands/nyldn/claude-octopus/scheduler/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/scheduler"><img src="https://agentmods.dev/badge/commands/nyldn/claude-octopus/scheduler.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.00887 |
| Opus 5 | $0.00008 | $0.00443 |
| Sonnet 5 | $0.00003 | $0.00177 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade B, and why
scheduler scanned grade B 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 6d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
helper="$(find "${HOME}/.claude/plugins/cache" "${HOME}/Library/Application Support/Claude" "${LOCALAPPDATA:-/dev/null}/Claude" "${XDG_DATA_HOME:-${HOME}/.local/share}/Claude" -maxdepth 8 -path "*/nyldn-plugins/octo/*/sc This is a copy
98% identical to octo-scheduler — 5 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scheduler
Manage the Claude Octopus scheduled workflow runner daemon.
MANDATORY COMPLIANCE — DO NOT SKIP
You MUST manage the scheduler only through the installed Octopus scheduler scripts after resolving the plugin root. You are PROHIBITED from:
- Reimplementing scheduler state changes manually
- Editing scheduler state files directly
- Skipping the plugin-root preflight because "I can do this faster directly"
Usage
Preflight — Ensure plugin root is resolvable (run via Bash tool FIRST):
OCTO_ROOT="${HOME}/.claude-octopus/plugin"
if [[ ! -x "$OCTO_ROOT/scripts/orchestrate.sh" ]]; then
helper="$OCTO_ROOT/scripts/helpers/ensure-plugin-root.sh"
if [[ ! -x "$helper" ]]; then
helper="$(find "${HOME}/.claude/plugins/cache" "${HOME}/Library/Application Support/Claude" "${LOCALAPPDATA:-/dev/null}/Claude" "${XDG_DATA_HOME:-${HOME}/.local/share}/Claude" -maxdepth 8 -path "*/nyldn-plugins/octo/*/scripts/helpers/ensure-plugin-root.sh" -print -quit 2>/dev/null)"
fi
[[ -x "$helper" ]] && bash "$helper" >/dev/null 2>&1 || true
fi
test -x "$OCTO_ROOT/scripts/orchestrate.sh" && echo "plugin-root:ok" || echo "plugin-root:missing"
If the output is plugin-root:missing, stop and ask the user to run /octo:setup.
${HOME}/.claude-octopus/plugin/scripts/scheduler/octopus-scheduler.sh start
${HOME}/.claude-octopus/plugin/scripts/scheduler/octopus-scheduler.sh stop
${HOME}/.claude-octopus/plugin/scripts/scheduler/octopus-scheduler.sh status
${HOME}/.claude-octopus/plugin/scripts/scheduler/octopus-scheduler.sh emergency-stop
Instructions for Claude
This command supports natural language. The user may invoke it with explicit subcommands OR with conversational requests. You MUST interpret intent and map to the correct action.
Step 1: Parse Intent
Map the user's input to one of these actions:
| Intent patterns | Action |
|---|---|
| "start", "run", "launch", "boot up", "turn on" | start |
| "stop", "shut down", "turn off", "kill", "halt" | stop |
| "status", "how is it", "what's running", "check", "is it running", no args | status |
| "emergency", "panic", "abort", "kill everything", "stop all" | emergency-stop |
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.
- 6d ago First seen · 96 lines · 15 tokens per session scan B fd0748da0f57
scheduler 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 887 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). It is 98% identical to octo-scheduler, differing in 5 lines, and is treated as a copy.
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.