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-intake)<a href="https://agentmods.dev/skills/nyldn/claude-octopus/skill-intake"><img src="https://agentmods.dev/badge/skills/nyldn/claude-octopus/skill-intake/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-intake"><img src="https://agentmods.dev/badge/skills/nyldn/claude-octopus/skill-intake.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.00034 | $0.01255 |
| Opus 5 | $0.00017 | $0.00628 |
| Sonnet 5 | $0.00007 | $0.00251 |
| Haiku 4.5 | $0.00003 | $0.00126 |
Grade A, and why
skill-intake 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 9d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intake
Work the incoming queue. Each item moves through a small set of states until it is either actionable by someone who did not write it, or closed with a reason.
A pull request is an issue with attached code. Same states, same moves, with
the deltas noted below. Resolving a bare #42 means checking both.
Adapted from triage in
mattpocock/skills (MIT), cut down to the
states this repo can actually represent and retargeted at gh and bd.
When To Use
- Open issues or PRs have accumulated and nobody knows which are real.
- A new report arrives and needs sorting before anyone works it.
- An issue has been sitting because it is not clear what it is asking for.
- Before planning, to establish what is actually in the queue.
When Not To Use
- To do the work an item describes. Triage decides what happens to it, not how.
- For local, private notes. That is
skill-issuesand.octo/ISSUES.md. - To review a PR's code quality. That is
skill-code-revieworskill-staged-review; intake decides whether the PR should be reviewed at all.
Inputs
An issue or PR reference, or nothing — with nothing, take the queue in order.
gh issue list and gh pr list for the public surface; bd ready and
bd blocked for tracked work.
Workflow
1. Categorise
What kind of thing is it: a bug, an enhancement, a question, or noise. For a PR, also: does it correspond to an existing issue, or arrive unannounced?
Do not skip this because the title looks obvious. Titles are written by people who already know what they meant.
2. Verify
The step that earns the whole skill. For a bug: reproduce it, or establish that you cannot. For a PR: check the claim it makes is the change it contains.
An unverified bug report is a hypothesis. Filing it as fact wastes whoever picks
it up. If reproduction needs something you do not have — credentials, a dataset,
a platform — that is needs-info, not verified.
3. Assign a state
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.
- 9d ago First seen · 130 lines · 34 tokens per session scan A 3c36e79edd31
skill-intake is a skill published in the GitHub repository nyldn/claude-octopus (4,056 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,255 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-08-30.
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…