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/wesammustafa/opencode-primer/reviewgit clone --depth 1 https://github.com/wesammustafa/opencode-primerWhat 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.00014 | $0.00233 |
| Opus 5 | $0.00007 | $0.00117 |
| Sonnet 5 | $0.00003 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00023 |
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 2d 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 a code review with these inputs:
- Scope:
$ARGUMENTSif provided, otherwise the current branch's diff vsmain. - Changed files (always check):
!git diff --name-only main...HEAD
For each changed file, evaluate (in this order):
- Correctness — bugs, race conditions, broken control flow.
- Security — input validation, auth, secrets, OWASP Top 10.
- Performance — N+1 queries, blocking I/O, unbounded loops.
- Maintainability — naming, duplication, missing tests.
Output one entry per finding using this format:
[Severity] <summary>
Where: <file:line>
Why: <one sentence>
Fix: <concrete snippet or instruction>
End with a one-line verdict: LGTM, Approve with comments, or Changes requested.
Do not edit any files in this command — leave the implementation to the developer.
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.
- 2d ago First seen · 32 lines · 14 tokens per session scan A 87b6f527e8c8
review is a command published in the GitHub repository wesammustafa/opencode-primer (384 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 233 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 commands, from other repositories
audit-quiz-coverage
Find quiz coverage gaps from recent guide/CHANGELOG/CC-releases changes and propose new questions.
retex
Retex - Capture lesson learned dans memory après fix, rollback, erreur.
cast
Choose, build, or synthesize the right harness for the current task.
fix
修复Bug并固化经验为skill/rule.
diagnose
RTK environment diagnostics - Checks installation, hooks, version, command routing.
spec
Generate a specification for AI-assisted implementation.