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.
npx skills add nyldn/claude-octopus --skill skill-prdgit 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/skills/nyldn/claude-octopus/skill-prd)<a href="https://agentmods.dev/skills/nyldn/claude-octopus/skill-prd"><img src="https://agentmods.dev/badge/skills/nyldn/claude-octopus/skill-prd.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00027 | $0.00820 |
| Opus 5 | $0.00014 | $0.00410 |
| Sonnet 5 | $0.00005 | $0.00164 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
skill-prd 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STOP - SKILL ALREADY LOADED
DO NOT call Skill() again. DO NOT load any more skills. Execute directly.
PHASE 0: CLARIFICATION (MANDATORY)
Before writing ANY PRD content, you MUST ask the user these questions:
I need to understand your requirements before creating the PRD.
1. **Target Users**: Who will use this? (developers, end-users, admins, etc.)
2. **Core Problem**: What specific pain point does this solve? Any metrics?
3. **Success Criteria**: How will you measure if this succeeds?
4. **Constraints**: Any technical, budget, or timeline constraints?
5. **Existing Context**: Is this greenfield or integrating with existing systems?
Please answer these (even briefly) so I can create a more targeted PRD.
WAIT for user response before proceeding to Phase 1.
If user says "skip" or provides the feature description inline, extract what you can and note assumptions.
PHASE 1: QUICK RESEARCH (Max 2 searches)
Only search if topic is unfamiliar. Limit to 2 web searches max:
- One for domain/market context
- One for technical patterns (if needed)
Do NOT over-research. 60 seconds max for this phase.
PHASE 2: WRITE PRD
Structure:
- Executive Summary - Vision + key value prop
- Problem Statement - Quantified pain points by user segment
- Goals & Metrics - SMART goals, P0/P1/P2 priority, success metrics table
- Non-Goals - Explicit boundaries (what we WON'T do)
- User Personas - 2-3 specific personas with use cases
- Functional Requirements - FR-001 format with acceptance criteria
- Implementation Phases - Dependency-ordered, time-boxed
- Risks & Mitigations - Top 3-5 risks with mitigation strategies
PHASE 2.5: ADVERSARIAL PRD REVIEW (RECOMMENDED)
After drafting the PRD but BEFORE self-scoring, dispatch the draft to a second provider for adversarial review. A single-model PRD has blind spots — cross-provider challenge surfaces wrong assumptions, uncovered scenarios, and contradictory requirements.
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.
- 8d ago First seen · 95 lines · 27 tokens per session scan A ac56c30b4586
skill-prd is a skill published in the GitHub repository nyldn/claude-octopus (4,056 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 820 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-08-30.
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.
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.
agent-native-audit
This skill should be used when conducting a scored agent-native architecture review. It launches 8 parallel sub-agents to audit action parity, context injection, CRUD completeness, capability discovery, and prompt-native features.