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/jcarlosrodicio/opencode-agent-orchestration-kit/reviewgit clone --depth 1 https://github.com/jcarlosrodicio/opencode-agent-orchestration-kitWrote 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/jcarlosrodicio/opencode-agent-orchestration-kit/review)<a href="https://agentmods.dev/commands/jcarlosrodicio/opencode-agent-orchestration-kit/review"><img src="https://agentmods.dev/badge/commands/jcarlosrodicio/opencode-agent-orchestration-kit/review.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 | $0.00013 | $0.00245 |
| Opus 5 | $0.00006 | $0.00122 |
| Sonnet 5 | $0.00003 | $0.00049 |
| Haiku 4.5 | $0.00001 | $0.00024 |
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 5d 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
Review the current diff and task against original evidence. Use git diff as
primary change evidence.
User arguments:
$ARGUMENTS
canonical_policy: required
review_stage: final
final_verdict_authority: reviewer
Load code-review-and-quality and apply its canonical policy. Core review is
always required. Select generic backend/frontend profiles from the changed
surface. Apply strict Clean Architecture, DDD, hexagonal, CQRS, or layered
profiles only when explicitly declared by the task or repository.
Inspect git status, the diff, applicable instructions, task/specification,
and original validation evidence. The developer summary is context, not
evidence. Do not modify files.
Only introduced or worsened problems may block. Report relevant pre-existing debt separately as non-blocking observations.
Return the canonical final envelope with review_stage: final, a verdict,
profile resolution, findings with causality, acceptance-criteria coverage,
validation rerun or not_run, residual risks, and a bounded correction
handoff when required.
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.
- 5d ago First seen · 36 lines · 13 tokens per session scan A 484294b3c036
review is a command published in the GitHub repository jcarlosrodicio/opencode-agent-orchestration-kit (107 stars, last pushed yesterday), licensed Apache-2.0. It adds 13 tokens to every session and 245 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
prime-pm-role
Prime the PM (project manager) persona for the headless session runner. Receives the user message as $ARGUMENTS.
prime-teammate-role
Prime the Teammate persona for the headless session runner. Receives the user message as $ARGUMENTS.
_prime-rails
These rails apply to every session-runner session (PM, Dev, and Teammate roles). Each role prime instructs you to read and apply this file before acting.
prime-dev-role
Prime the Dev (developer) persona for the headless session runner. No task is present in $ARGUMENTS — the runner will relay the PM's first instruction separately.
update
Bring this machine to latest main — sync deps, verify environment, restart services. Runs deterministically via inline bash execution, not model discretion.
dispatch-worker
Run one in-session-agent Worker tick (RFC-0041 §4.3.1).