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/octopusreview/octopus-pluginWrote 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/octopusreview/octopus-plugin/octopus-review)<a href="https://agentmods.dev/commands/octopusreview/octopus-plugin/octopus-review"><img src="https://agentmods.dev/badge/commands/octopusreview/octopus-plugin/octopus-review/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/octopusreview/octopus-plugin/octopus-review"><img src="https://agentmods.dev/badge/commands/octopusreview/octopus-plugin/octopus-review.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.00018 | $0.00236 |
| Opus 5 | $0.00009 | $0.00118 |
| Sonnet 5 | $0.00004 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
octopus-review 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 11d 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.
What it actually says
Run an Octopus code review. What to review depends on $ARGUMENTS:
A pull request — when $ARGUMENTS is a PR number or PR URL
Call the octopus_review_pr tool with pr set to $ARGUMENTS and repoPath set to the current repository root. Octopus reviews the PR server-side and posts its findings as comments on the pull request. This is asynchronous, so tell the user the review has started and that findings will appear on the PR. The repository must already be connected to Octopus.
Working changes — when $ARGUMENTS is empty
Call the octopus_review_changes tool with repoPath set to the current repository root, so Octopus reviews the uncommitted (then staged) diff. Present the findings grouped by severity, then offer to fix the highest-severity items.
If the token is missing, run octopus_status and tell the user to add an oct_ token to the plugin config.
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.
- 11d ago First seen · 17 lines · 18 tokens per session scan A 5b0764d24e99
octopus-review is a command published in the GitHub repository octopusreview/octopus-plugin (0 stars, last pushed 10d ago), licensed MIT. It adds 18 tokens to every session and 236 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-31.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.