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 agentmods add commands/nyldn/claude-octopus/sentinelgit 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/sentinel)<a href="https://agentmods.dev/commands/nyldn/claude-octopus/sentinel"><img src="https://agentmods.dev/badge/commands/nyldn/claude-octopus/sentinel.svg" alt="Measured on agentmods" 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.00016 | $0.00889 |
| Opus 5 | $0.00008 | $0.00445 |
| Sonnet 5 | $0.00003 | $0.00178 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
sentinel 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 today.
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sentinel (/octo:sentinel)
Your first output line MUST be: 🐙 Octopus Sentinel
GitHub-aware work monitor that triages issues, PRs, and CI failures. Sentinel observes and recommends workflows but never auto-executes them.
MANDATORY COMPLIANCE — DO NOT SKIP
When the user explicitly invokes /octo:sentinel, you MUST run the Sentinel orchestrator path below. You are PROHIBITED from manually guessing repository status, skipping GitHub checks, or starting remediation without explicit user approval.
Usage
/octo:sentinel # One-time triage scan
/octo:sentinel --watch # Continuous monitoring
/octo:sentinel --canary # Post-deploy canary monitoring
Scheduled Claude Code Web Usage
For recurring triage, schedule Sentinel as a read-only Claude Code web or hosted task. Use /octo:sentinel for the normal scan and /octo:sentinel --canary https://example.com for post-deploy monitoring.
Scheduled Sentinel should stay triage-only. It may recommend /octo:debug,
/octo:review, or /octo:embrace, but it must not start remediation unless
the user explicitly asks for it.
What Sentinel Monitors
| Source | Filter | Recommended Action |
|---|---|---|
| Issues | octopus label |
Classified via task type → workflow recommendation |
| PRs | Review requested | /octo:review for code review |
| CI Runs | Failed status | /octo:debug for investigation |
Environment Variables
| Variable | Default | Description |
|---|---|---|
OCTOPUS_SENTINEL_ENABLED |
false |
Must be true to activate |
OCTOPUS_SENTINEL_INTERVAL |
600 |
Poll interval for --watch mode (seconds) |
Safety
Sentinel is triage-only. It:
- Reads GitHub state (issues, PRs, CI runs)
- Classifies and recommends workflows
- Writes findings to
.octo/sentinel/triage-log.md - Never auto-executes any workflow
Requirements
- GitHub CLI (
gh) must be installed and authenticated - Repository must be a GitHub repository
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.
- today First seen · 101 lines · 16 tokens per session scan A 6b29e28c7d4e
sentinel is a command published in the GitHub repository nyldn/claude-octopus (4,045 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 889 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-05.
Other commands, from other repositories
renovate
Generate renovate.json covering all dependency file types used in a repo, emit a GitHub Actions workflow that validates renovate.json on every PR, or generate a pre-commit hook for local validation.
composite-actions
Generate, review, secure, and test composite GitHub Actions following best practices — full repo scaffold, interview-driven generation, PR creation on existing repos, SHA pinning, secrets-as-inputs, job summaries, and actionlint validation.
github-actions
Design, review, secure, and debug GitHub Actions workflows — reusable workflows, OIDC federation, SHA pinning, token scoping, promotion orchestration, and CI failure diagnosis.
trivy
Scan container images, filesystems, git repos, and existing SBOMs for CVEs, secrets, and license violations using Trivy. Covers local CLI, CI severity gates with SARIF upload, and continuous monitoring via Trivy Operator (Flux HelmRelease). Use when asked to "scan my image", "check for CVEs", "scan this repo for…
dora
Measure, benchmark, instrument, and debug DORA metrics (Deployment Frequency, Lead Time for Changes, Change Failure Rate, MTTR) for production engineering teams. Covers GitHub Actions instrumentation, Prometheus recording rules, Grafana dashboards, incident source integration, SaaS tool selection, and anti-pattern…
nyann:watch
Start (or stop) a CI sentinel for the current repo's open PRs — a one-shot foreground poll by default, or a supervised background daemon with --daemon. Also manage a multi-repo watch-list and poll every watched repo at once. Notifications surface in your next session via the session-start hook.