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 jamestorrevillas/dev-skills --skill code-reviewgit clone --depth 1 https://github.com/jamestorrevillas/dev-skillsWrote 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/jamestorrevillas/dev-skills/code-review)<a href="https://agentmods.dev/skills/jamestorrevillas/dev-skills/code-review"><img src="https://agentmods.dev/badge/skills/jamestorrevillas/dev-skills/code-review/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/jamestorrevillas/dev-skills/code-review"><img src="https://agentmods.dev/badge/skills/jamestorrevillas/dev-skills/code-review.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.00062 | $0.01148 |
| Opus 5.5 | $0.00025 | $0.00459 |
| Sonnet 5.5 | $0.00012 | $0.00230 |
| Haiku 4.5 | $0.00006 | $0.00115 |
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 1mo 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Review Philosophy
Review the code, not the person. The goal is to ship better software, not to win arguments. Every comment should make the codebase better or help the author learn — preferably both.
Feedback Categories
Always tag review comments to set expectations:
| Tag | Meaning | Must Fix? |
|---|---|---|
BLOCKER |
Breaks functionality, security risk, violates standards | Yes |
WARNING |
Technical debt, potential issue, should be addressed | Recommended |
SUGGESTION |
Optional improvement, alternative approach | No |
QUESTION |
Asking for clarification or understanding | No |
NITPICK |
Minor style or preference | Author decides |
PRAISE |
Acknowledge good work | N/A |
Code Quality Checklist
Correctness
- Does the code do what the ticket/story requires?
- Are edge cases handled? (null, empty, boundary values)
- Is error handling present and meaningful?
- Are async operations awaited properly?
- Are there any obvious race conditions?
Readability
- Are variable and function names descriptive?
- Is the code self-documenting (minimal need for comments)?
- Are complex sections commented with the "why"?
- Is there dead code or commented-out code that should be removed?
- Is function length reasonable (< 40 lines as a guideline)?
Architecture
- Does this follow the existing patterns in the codebase?
- Is there unnecessary coupling between modules?
- Is the change in the right layer (controller vs service vs repository)?
- Would this be hard to test? (if yes, it needs refactoring)
- Is this solving the right problem at the right level?
Performance
- Are there N+1 query problems (loops that trigger individual DB queries)?
- Are expensive operations cached where appropriate?
- Is pagination implemented for list endpoints?
- Are there unnecessary re-renders (frontend)?
Tests
- Are tests included for new behavior?
- Do tests cover the happy path AND error paths?
- Are tests testing behavior, not implementation details?
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.
- 1mo ago First seen · 144 lines · 0 tokens per session scan A f177c39fa1f8
code-review is a skill published in the GitHub repository jamestorrevillas/dev-skills (3 stars, last pushed 7mo ago), licensed MIT. It adds 62 tokens to every session and 1,148 once invoked, about $0.0002 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-31.
Other skills, from other repositories
architecture-audit
Comprehensive project consistency review across code, documentation, diagrams, and configuration.
semantic-codebase-intelligence
Deep structural analysis of a codebase—dependency mapping, architecture boundary detection, coupling/cohesion scoring, and dead code discovery. Use when asked to "analyze codebase structure", "map dependencies", "find dead code", "architecture analysis", "coupling analysis", "trace dependencies", or "understand this…
code-review
Systematic code review for correctness, security, and growth — not just style enforcement.
deep-review
Adversarial code review with three parallel perspectives — Advocate, Skeptic, Architect — that create productive tension. Use for high-stakes PRs, architectural changes, or when single-pass review would miss issues. Surfaces findings through disagreement, not consensus.
extension-audit-methodology
Systematic 5-dimension audit framework for VS Code extensions — debug hygiene, dead code, performance, menu validation, dependency cleanup.
parity-guard-test-pattern
When checking that all callers of a contract implement it correctly, you get false positives from wrapper delegators.