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 skills add akshan-main/review-by-opp --skill statusgit clone --depth 1 https://github.com/akshan-main/review-by-oppWrote 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/akshan-main/review-by-opp/status)<a href="https://agentmods.dev/skills/akshan-main/review-by-opp/status"><img src="https://agentmods.dev/badge/skills/akshan-main/review-by-opp/status/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/skills/akshan-main/review-by-opp/status"><img src="https://agentmods.dev/badge/skills/akshan-main/review-by-opp/status.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.00033 | $0.00433 |
| Opus 5 | $0.00016 | $0.00217 |
| Sonnet 5 | $0.00007 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
review-by-opp:status 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 10d 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
Show the current review-by-opp session status.
What to do
-
Load the ledger:
- Read
reviews/current.json - If missing, tell user: "No active session. Run
/review-by-opp:startfirst."
- Read
-
Display status table:
Field Value Session {session_id short}Round {current_round} / {max_rounds} Total findings {count} Open {open count} Blocking open {blocking count} Resolved {resolved count} Review scope {scope} Can finalize Yes/No Verdict {verdict or "in progress"} -
Display agent configuration:
Agent Setting Value Claude Model user-controlled Claude Effort user-controlled Codex Config mode inherited/overridden Codex Model {effective model or "default"} Codex Reasoning {reasoning effort or "default"} -
If there are blocking reasons, list them.
-
Show open findings in compact format:
[open] f-1-abc123 high/bug: Null pointer (src/main.ts:42)
-
Show next actions:
- If can finalize: "Ready to finalize. Run
/review-by-opp:finalize" - If blocking findings exist: "Resolve blocking findings with
/review-by-opp:fix" - If no review has been run yet: "Run
/review-by-opp:reviewto start the first review"
- If can finalize: "Ready to finalize. Run
$ARGUMENTS
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.
- 10d ago First seen · 50 lines · 33 tokens per session scan A 590da5068579
review-by-opp:status is a skill published in the GitHub repository akshan-main/review-by-opp (6 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 433 once invoked, about $0.0002 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 skills, from other repositories
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-spec-completion-review
Verify that a spec's completed tasks fully implement the spec requirements. Use at spec completion before close.
flow-next-plan-review
Carmack-level review of a flow-next spec or plan via the configured backend. Use when asked to review a plan or spec.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
flow-next-worktree-kit
Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
pr
Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.