octo-research

octo-research is a command for Claude Code, Cursor from nyldn/claude-octopus. It costs 9 tokens per session (1,262 once invoked), scanned A, original, MIT.

A research command that gathers information from multiple AI providers and combines it into a detailed analysis.

In plain words
What is it for?
Use it to investigate questions, compare sources, and produce a synthesized research result.
Why use it?
It reduces the need to research a topic manually or rely on one AI model. It also enforces a structured workflow for broader research.

Command for Claude CodeCursor

Written for Claude Code and Cursor: disable-model-invocation in frontmatter, but also a Cursor plugin manifest. Also seen: names the AskUserQuestion tool; mentions Codex.

Part of the octo plugin — 70 skills, 106 commands, 10 agents, 18 hooks shipped together

Good fit Use it to investigate questions, compare sources, and produce a synthesized research result.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/nyldn/claude-octopus/octo-research
About the project

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.

nyldn/claude-octopus · 4,061 stars · on GitHub · reddit.com

Install

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.

Clone the repo
git clone --depth 1 https://github.com/nyldn/claude-octopus

Made for: Claude Code, Cursor.

Or install octo, the plugin that ships this one along with the rest of its 70 skills, 106 commands, 10 agents, 18 hooks.

Wrote 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.

agentmods badge for octo-research

README.md
[![agentmods](https://agentmods.dev/badge/commands/nyldn/claude-octopus/octo-research/github.svg)](https://agentmods.dev/commands/nyldn/claude-octopus/octo-research)
Your own site
<a href="https://agentmods.dev/commands/nyldn/claude-octopus/octo-research"><img src="https://agentmods.dev/badge/commands/nyldn/claude-octopus/octo-research/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.

agentmods 80×15 button for octo-research

Your own site · 80×15
<a href="https://agentmods.dev/commands/nyldn/claude-octopus/octo-research"><img src="https://agentmods.dev/badge/commands/nyldn/claude-octopus/octo-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,262 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00009 $0.01262
Opus 5 $0.00005 $0.00631
Sonnet 5 $0.00002 $0.00252
Haiku 4.5 $0.00001 $0.00126

Measured 8d ago against content hash de136f0467a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

octo-research 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 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.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • research — 97% identical, 3 lines differ
.cursor-plugin/commands/octo-research.md · 143 lines

How it starts

The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Research - Deep Multi-AI Research

Your first output line MUST be: 🐙 Octopus Research

🤖 INSTRUCTIONS FOR CLAUDE

MANDATORY COMPLIANCE — DO NOT SKIP

When the user explicitly invokes /octo:research, you MUST execute the structured research workflow below. You are PROHIBITED from answering directly, skipping the multi-provider research, or deciding the topic is "too simple" for deep research. The user chose this command deliberately — respect that choice.

EXECUTION MECHANISM — NON-NEGOTIABLE

You MUST execute this command by reading and following the dedicated research source. You are PROHIBITED from:

  • ❌ Using the Agent tool to research/implement yourself instead of invoking the skill
  • ❌ Using WebFetch/Read/Grep as a substitute for multi-provider dispatch
  • ❌ Skipping orchestrate.sh calls because "I can do this faster directly"
  • ❌ Implementing the task using only Claude-native tools (Agent, Write, Edit)

Multi-LLM orchestration is the purpose of this command. If you execute using only Claude, you've violated the command's contract.


When the user invokes this command (e.g., /octo:research <arguments>):

Step 1: Resolve Research Breadth/Intensity

First parse explicit flags from the user's arguments:

  • --breadth=light|standard|exhaustive
  • --intensity=quick|standard|deep

Map breadth to intensity when intensity is absent:

  • light -> quick
  • standard -> standard
  • exhaustive -> deep

If neither flag is present, use the AskUserQuestion tool to select intensity:

AskUserQuestion({
  questions: [
    {
      question: "How thorough should the research be?",
      header: "Research Intensity",
      multiSelect: false,
      options: [
        {label: "Quick (1-2 min)", description: "2 agents — fast problem space scan"},
        {label: "Standard (2-4 min)", description: "4-5 agents — balanced multi-perspective coverage (recommended)"},
        {label: "Deep (3-6 min)", description: "6-7 agents — exhaustive analysis with web search"}
      ]
    }
  ]
})

Read the full file on GitHub · 143 lines

Changes

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.

  1. 8d ago First seen · 143 lines · 9 tokens per session scan A de136f0467a1

Subscribe to this mod's changes

octo-research is a command published in the GitHub repository nyldn/claude-octopus (4,061 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 1,262 once invoked, about $0.0000 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-03.