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 skills/aiocean/claude-plugins/aio-review-quicknpx skills add aiocean/claude-plugins --skill aio-review-quickgit clone --depth 1 https://github.com/aiocean/claude-pluginsWrote 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/aiocean/claude-plugins/aio-review-quick)<a href="https://agentmods.dev/skills/aiocean/claude-plugins/aio-review-quick"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-review-quick.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.00048 | $0.00717 |
| Opus 5 | $0.00024 | $0.00358 |
| Sonnet 5 | $0.00010 | $0.00143 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
aio-review-quick 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review — Post-Implementation Check
Environment
- GitNexus: !
npx gitnexus status 2>/dev/null && echo "AVAILABLE" || echo "NOT INSTALLED"
Review completed work using change detection, duplication detection, and type checking.
Prerequisites
- Baseline snapshot from
/aio-snapshot - GitNexus indexed (
npx gitnexus analyze) for duplication check - LSP for diagnostics
Workflow
Step 1: Change detection (GitNexus)
detect_changes()
For each changed file, get symbol context:
context(file)
Step 2: Duplication check (GitNexus)
For each new function or significant code block, use the GitNexus MCP query tool:
query("description of new code")
Flag if similarity >0.75 — potential duplication or missed reuse.
Step 3: Convention check (GitNexus)
query("pattern used in new code")
Verify new code follows existing conventions.
Step 4: Type safety (LSP)
lsp_diagnostics(file) → errors in changed files
lsp_diagnostics_directory(dir) → broader check
Step 5: Output review report
## Review: [what was implemented]
### Changes (from detect_changes)
- `file-a.ts`: Added `fnX`, modified `fnY`
- `file-b.rs`: Added struct `Z`, new command `cmd`
### Duplication Check
- OK: No similar code found for `fnX`
- WARNING: `fnY` is 78% similar to `existingFn` in `other.ts`
### Convention Check
- OK: Follows pattern from `similar-file.ts`
- NOTE: [any deviations]
### Type Safety
- N errors, M warnings
### Checklist
- [ ] Logic in correct layer? (backend vs frontend)
- [ ] No duplicated business logic? (SSOT)
- [ ] Proper fix, not a workaround?
- [ ] Easy to change tomorrow? (iteration-first)
Quick Review (small changes, <3 files)
Skip change detection. Just run:
lsp_diagnosticson changed files- One GitNexus duplication search via
query - Quick convention check
Skill Graph — What to invoke next
After review completes:
| Result | Next skill |
|---|---|
| Review clean, ready to merge | /superpowers:verification-before-completion → /superpowers:finishing-a-development-branch |
| Issues found, needs fixes | Fix issues → re-run /aio-review-quick |
| Needs full code review (security, architecture) | /aio-review-deep — parallel multi-agent review with OMC agents |
| Want to extract learnings | /aio-reflect — capture knowledge from this session |
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 · 106 lines · 48 tokens per session scan A 6c9e76411706
aio-review-quick is a skill published in the GitHub repository aiocean/claude-plugins (4 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 717 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
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
source-command-methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
canary
Post-deploy monitoring: watch production after a deploy and alert on regressions.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.
investigate
Systematic root-cause debugging: find the cause before writing any fix.
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.