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/skillsland/opencode-plugin-cc/reviewgit clone --depth 1 https://github.com/skillsland/opencode-plugin-ccWhat 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 | $0.00011 | $0.00646 |
| Opus 5 | $0.00005 | $0.00323 |
| Sonnet 5 | $0.00002 | $0.00129 |
| Haiku 4.5 | $0.00001 | $0.00065 |
Grade A, and why
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 yesterday.
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 a read-only OpenCode review through the shared plugin runtime.
Raw slash-command arguments:
$ARGUMENTS
Core constraint:
- This command is review-only.
- Do not fix issues, apply patches, or suggest that you are about to make changes.
- Your only job is to run the review and return OpenCode's output verbatim to the user.
Execution mode rules:
- If the raw arguments include
--wait, do not ask. Run the review in the foreground. - If the raw arguments include
--background, do not ask. Run the review in a Claude background task. - Otherwise, estimate the review size before asking:
- For working-tree review, start with
git status --short --untracked-files=all. - For working-tree review, inspect
git diff --shortstat --cachedandgit diff --shortstat. - For base-branch review, use
git diff --shortstat <base>...HEAD. - Treat untracked files or directories as reviewable work.
- Recommend waiting only when the scoped review is clearly tiny, roughly 1-2 files total.
- In every other case, including unclear size, recommend background.
- For working-tree review, start with
- Then use
AskUserQuestionexactly once with two options, putting the recommended option first and suffixing its label with(Recommended):Wait for resultsRun in background
Argument handling:
- Preserve the user's arguments exactly.
- Do not strip
--waitor--backgroundyourself. /opencode:reviewdoes not accept custom focus text. Use/opencode:adversarial-reviewfor steerable review.- The companion script parses
--waitand--background, but Claude Code'sBash(..., run_in_background: true)is what actually detaches the run.
Foreground flow:
- Run:
node "${CLAUDE_PLUGIN_ROOT}/dist/scripts/opencode-companion.mjs" review "$ARGUMENTS"
- Return the command stdout verbatim, exactly as-is.
- Do not fix any issues mentioned in the review output.
Background flow:
- Launch the review with
Bashin the background:
Bash({
command: `node "${CLAUDE_PLUGIN_ROOT}/dist/scripts/opencode-companion.mjs" review "$ARGUMENTS"`,
description: "OpenCode review",
run_in_background: true,
});
- Do not call
BashOutputor wait for completion in this turn. - After launching the command, tell the user: "OpenCode review started in the background. Check
/opencode:statusfor progress."
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.
- yesterday First seen · 66 lines · 11 tokens per session scan A 1bde9a8b6c64
review is a command published in the GitHub repository skillsland/opencode-plugin-cc (1 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 646 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
psm
/oh-my-claudecode:psm is a compatibility alias for /oh-my-claudecode:project-session-manager.
plan-review
The core plan review flow across Claude Code, Codex, and other supported agent hosts.
release
Ship a stable cmux release built by CI: bump version, update changelog, open a PR, merge, tag, then GitHub Actions builds, signs, and publishes.
refresh-compare-pages
Freshly research, add, and refresh marketing compare pages, then open a descriptive PR.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
step-research
Always research before proposing a fix. The Untether bug you're chasing is often a known upstream engine quirk, a previously-fixed regression, or a documented config gotcha.