oh-my-opencode-slim is a plugin that coordinates multiple specialized AI agents inside OpenCode, assigning codebase exploration, documentation research, architecture review, design, and implementation to different agents. It is for developers who want agent teams to divide and reconcile software-development work while mixing models from different providers. The catalogue entries are the plugin’s bundled agents, skills, and instruction.
Borrowing it
Nothing to install: this file belongs to alvinunreal/oh-my-opencode-slim. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/alvinunreal/oh-my-opencode-slim/master/.agents/skills/cli-review/SKILL.mdgit clone --depth 1 https://github.com/alvinunreal/oh-my-opencode-slimWrote 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/alvinunreal/oh-my-opencode-slim/cli-review)<a href="https://agentmods.dev/skills/alvinunreal/oh-my-opencode-slim/cli-review"><img src="https://agentmods.dev/badge/skills/alvinunreal/oh-my-opencode-slim/cli-review.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Supply Chain · line 47 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
- high Tool Misuse · line 47 Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
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.00061 | $0.00524 |
| Opus 5 | $0.00030 | $0.00262 |
| Sonnet 5 | $0.00012 | $0.00105 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade C, and why
cli-review scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL "https://greptile.com/cli/install" | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash(git:*) Bash(greptile:*) Bash(command:*) Bash(curl:*) Bash(npm:*) Copies of this mod
6 near-identical copies found in the catalogue:
- cli-review — 100% identical, 0 lines differ
- cli-review — 100% identical, 0 lines differ
- cli-review — 100% identical, 0 lines differ
- cli-review — 100% identical, 0 lines differ
- cli-review — 100% identical, 0 lines differ
- cli-review — 100% identical, 0 lines differ
What it actually says
CLI Review
Run a Greptile review from the local checkout and summarize the findings.
Instructions
1. Confirm repository context
Start from the current repository root:
git rev-parse --show-toplevel
If the command fails, tell the user that the Greptile CLI review must be run from a git repository.
2. Check for the Greptile CLI
Check whether greptile is installed:
command -v greptile
If it is missing, do not install it automatically. Ask the user for permission, then show the recommended install command:
npm i -g greptile
If npm is unavailable, offer the shell installer fallback:
curl -fsSL "https://greptile.com/cli/install" | sh
After installation, re-run command -v greptile.
3. Ensure authentication
Check the signed-in account:
greptile whoami
If the CLI reports that authentication is missing, run:
greptile login
Wait for the user to complete the login flow before continuing.
4. Run the review
Prefer JSON output:
greptile review --json
If JSON output is unsupported or fails with a usage error, fall back to:
greptile review --agent
Do not hide the raw command failure if both commands fail. Summarize the failing command and the next action the user needs to take.
5. Summarize results
Parse JSON output when available and report:
- Review status
- Number of findings
- Highest severity findings first
- Files that need edits
- Suggested next command or fix path
When output is plain text, preserve the same structure as much as possible. Keep the summary concise and focused on actionable findings.
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 · 61 tokens per session scan C 56a93ea9d5da
cli-review is a skill published in the GitHub repository alvinunreal/oh-my-opencode-slim (8,704 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 524 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
rust-patterns
Rust patterns covering ownership, lifetimes, error handling, traits, async with Tokio, and smart pointers. Activate when writing or reviewing Rust.
decision-trace
Record why the agent changed something, what evidence was used, and what assumptions were made — so code reviews become much faster.
code-review
Review code for security vulnerabilities, logic errors, and quality issues. Returns findings ranked by severity with remediation steps.
arch-constraint-guard
Block edits that violate known system boundaries, team rules, service contracts, or domain-layer separation. Reads rules from /.fd-plan/ /.codebase/CONSTRAINTS.md.
blast-radius-preview
Show the likely downstream consequences of a proposed change — hidden dependencies, fragile integration points, and predicted breakage categories.
test-gap-detector
Identify which areas of a proposed change are weakly covered by tests and suggest the minimum high-value tests to add first.