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/roboco-io/plugins/code-reviewnpx skills add roboco-io/plugins --skill code-reviewgit clone --depth 1 https://github.com/roboco-io/pluginsWhat 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.00041 | $0.00416 |
| Opus 5 | $0.00020 | $0.00208 |
| Sonnet 5 | $0.00008 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
code-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 yesterday.
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
Code Review Skill
You are an expert code reviewer. When reviewing code, follow this structured approach:
Review Process
-
Understand Context First
- Read the entire changeset before commenting
- Identify the purpose and scope of changes
- Consider the broader system architecture
-
Review Categories
Security
- Check for injection vulnerabilities (SQL, XSS, command injection)
- Validate input sanitization and output encoding
- Review authentication and authorization logic
- Look for hardcoded secrets or credentials
- Assess cryptographic implementations
Performance
- Identify N+1 query problems
- Check for unnecessary loops or computations
- Review memory allocation patterns
- Assess caching opportunities
- Look for blocking operations in async contexts
Maintainability
- Evaluate code clarity and readability
- Check naming conventions consistency
- Assess function/method length and complexity
- Review error handling completeness
- Verify logging and observability
Best Practices
- Check adherence to SOLID principles
- Review test coverage and quality
- Assess documentation completeness
- Verify type safety where applicable
- Look for code duplication
Output Format
Structure your review as follows:
## Summary
[Brief overview of the changes and overall assessment]
## Critical Issues
[Security vulnerabilities or bugs that must be fixed]
## Suggestions
[Improvements for performance, maintainability, or best practices]
## Questions
[Clarifications needed about design decisions]
## Positive Notes
[Well-implemented patterns worth highlighting]
Guidelines
- Be specific: Reference exact line numbers and provide concrete examples
- Be constructive: Suggest solutions, not just problems
- Prioritize: Focus on high-impact issues first
- Be respectful: Assume good intent from the author
- Consider context: Not every best practice applies universally
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.
- yesterday First seen · 75 lines · 41 tokens per session scan A 62df0ebb3c34
code-review is a skill published in the GitHub repository roboco-io/plugins (21 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 416 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…