Borrowing it
Nothing to install: this file belongs to modiqo/skillspec. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/modiqo/skillspec/main/.claude/skills/code-review/source/SKILL.mdgit clone --depth 1 https://github.com/modiqo/skillspecWrote 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/modiqo/skillspec/source)<a href="https://agentmods.dev/skills/modiqo/skillspec/source"><img src="https://agentmods.dev/badge/skills/modiqo/skillspec/source/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/modiqo/skillspec/source"><img src="https://agentmods.dev/badge/skills/modiqo/skillspec/source.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 48 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 106 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00116 | $0.02842 |
| Opus 5.5 | $0.00046 | $0.01137 |
| Sonnet 5.5 | $0.00023 | $0.00568 |
| Haiku 4.5 | $0.00012 | $0.00284 |
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 2mo 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Orchestrate a multi-agent code review pipeline: research the changes, optionally investigate external alternatives, dispatch parallel domain-specific reviewers, and synthesize everything into a structured report.
Input Collection
Prompt the user to select an input mode. Present these options clearly:
What would you like me to review?
- Current PR — review the open PR on this branch (description + diff)
- Diff to main — review all uncommitted and committed changes vs main
- Specific paths — review specific files, crates, or directories
Pick a number, or describe what you'd like reviewed.
Collecting the diff
Mode 1 — Current PR:
gh pr view --json title,body,number,baseRefName
gh pr diff
If no open PR exists, tell the user and suggest mode 2 instead.
Mode 2 — Diff to main:
git diff main...HEAD
Also include git log main..HEAD --oneline for commit context.
Mode 3 — Specific paths: Ask the user for paths. Read the specified files directly. No diff — review the code as-is.
Store the collected input (diff text, PR description, file contents) for use in subsequent phases.
Handling large diffs
If the diff exceeds ~2000 lines, save it to a temporary file (/tmp/code-review-diff.patch) and have agents read it via the Read tool rather than inlining it in their prompts. This prevents context overflow. Reference the file path in agent prompts instead of pasting the diff.
Phase 1: Research & Domain Mapping
Spawn an Agent (subagent_type: general-purpose) and include the full text of the research-codebase skill instructions in its prompt (read .claude/skills/research-codebase/SKILL.md first). Direct the agent to research the changes with this focus:
- Map all changed files to their logical domains and crate boundaries
- Identify which changes are Rust code vs non-Rust (CI, docs, config, TypeScript SDK, nix, etc.)
- Understand the architectural context around each change — what traits, types, and modules are involved
- Group changes into at most 4 logical domain groups, merging smaller related changes together
- Flag any changes that warrant external web research:
- New dependencies or crate additions
- Unfamiliar architectural patterns
- Potentially deprecated API usage
- Cases where alternative approaches might exist
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.
- 2mo ago First seen · 233 lines · 116 tokens per session scan A 4f7600536360
code-review is a skill published in the GitHub repository modiqo/skillspec (699 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 116 tokens to every session and 2,842 once invoked, about $0.0005 per session on Opus 5.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
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.