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 resumegit 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/resume)<a href="https://agentmods.dev/skills/akshan-main/review-by-opp/resume"><img src="https://agentmods.dev/badge/skills/akshan-main/review-by-opp/resume/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/resume"><img src="https://agentmods.dev/badge/skills/akshan-main/review-by-opp/resume.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.00025 | $0.00328 |
| Opus 5 | $0.00013 | $0.00164 |
| Sonnet 5 | $0.00005 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
review-by-opp:resume 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 11d 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
Resume an existing review-by-opp session.
What to do
-
Load the ledger:
- Read
reviews/current.json - If missing, tell user: "No active session to resume. Run
/review-by-opp:startfirst." - If the session has a
final_verdictset, tell user: "This session is already finalized with verdict: {verdict}. Run/review-by-opp:startto begin a new session."
- Read
-
Show session summary:
- Session ID, when it was started, current round
- Number of open findings, blocking findings
- Last round verdict if available
-
Suggest next action based on state:
- If there are unresolved findings from the last review: "You have {N} open findings from round {R}. Use
/review-by-opp:fixto address them." - If fixes were applied but no new review has run: "Fixes were applied. Run
/review-by-opp:reviewfor the next Codex review round." - If no review has been run yet: "Session initialized but no review yet. Run
/review-by-opp:review."
- If there are unresolved findings from the last review: "You have {N} open findings from round {R}. Use
-
Restate the rules:
Reminder: All blocking findings must be explicitly resolved before this session can be finalized. The stop gate enforces this.
$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.
- 11d ago First seen · 30 lines · 25 tokens per session scan A 8a43fb711ff2
review-by-opp:resume is a skill published in the GitHub repository akshan-main/review-by-opp (6 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 328 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 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.