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 codebygarv/Ai-skills --skill code-reviewergit clone --depth 1 https://github.com/codebygarv/Ai-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/codebygarv/ai-skills/code-reviewer)<a href="https://agentmods.dev/skills/codebygarv/ai-skills/code-reviewer"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/code-reviewer/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/codebygarv/ai-skills/code-reviewer"><img src="https://agentmods.dev/badge/skills/codebygarv/ai-skills/code-reviewer.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.00046 | $0.00488 |
| Opus 5.5 | $0.00018 | $0.00195 |
| Sonnet 5.5 | $0.00009 | $0.00098 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
code-reviewer 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Provide a thorough, general-purpose code review covering correctness, readability, maintainability, and performance — the kind of review a careful senior engineer would leave on a diff.
When to Use
- Reviewing a diff, PR, file, or function before merge.
- The user asks for "a code review" without narrowing to a specific concern (security, types, performance) — those narrower concerns have their own skills (Security Auditor, TypeScript Guardian, Performance Auditor) and this skill should defer to them for deep dives in those areas while still flagging obvious issues.
What to Analyze
- Correctness — logic errors, off-by-ones, incorrect assumptions about inputs, unhandled null/undefined/empty cases.
- Readability — naming, function length, nesting depth, whether intent is obvious without extra explanation.
- Maintainability — duplication, tight coupling, magic numbers/strings, missing abstraction where a pattern repeats 3+ times.
- Performance — obviously wasteful operations (N+1 queries, unnecessary re-computation, quadratic loops over data that can grow).
- Consistency — does it match the surrounding codebase's existing patterns and conventions.
- Error handling — are failure paths handled, or silently swallowed/ignored.
Output Format
- Group findings by severity: Blocking (bugs, correctness issues) → Should Fix (maintainability, missing error handling) → Nit (style, naming).
- Each finding: file/line reference, what's wrong, and a concrete suggested fix — not just "this could be better."
- End with what's done well, briefly — but only if genuinely true, not as a formality.
Avoid
- Rewriting the whole file as "feedback" instead of pointing at specific issues.
- Nitpicking style that a linter/formatter already enforces.
- Flagging a pattern as wrong when it's actually the codebase's established convention — check for consistency first.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 35 lines · 46 tokens per session scan A 774a2064362e
code-reviewer is a skill published in the GitHub repository codebygarv/Ai-skills (27 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 488 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-30.
Other skills, from other repositories
bun-api
Bun runtime API reference for TypeScript scripts. Covers Bun.serve() HTTP/HTTP/2 server with routes and WebSockets, fetch() transport options, proxies and Bun.FetchSession connection pools, Bun.ModuleGraph multi-instance apps, Bun.file(), Bun.write(), Bun.$() shell, Bun.spawn(), Bun.Glob, Bun.env, bun:sqlite…
bun-cli
Bun CLI reference for package management, script running, type checking, testing, bundling, and compilation. Covers bun install/add/remove/update, bun run, bun check and --check, bun test, bun build, bunx, bun patch, bun audit fix, bun dedupe, bun prune, bun why, bun pm, bun repl, bunfig.toml, bun.lock, workspace…
git-pr
PR and MR workflows for GitHub (gh) and GitLab (glab). Creation, review comment handling, thread resolution, review state queries, merging, cost-aware bot review rounds (GitHub: Copilot, CodeRabbit), and Copilot code review configuration (rulesets, custom instructions, billing). Use when creating PRs/MRs, addressing…
deps-upgrade
Validate JavaScript/TypeScript dependency upgrades after an interactive or manual update. Establish the real delta from git, detect peer/engine/type conflicts, extract breaking changes, migrations and adoptable features from release notes, assess held-back or seemingly unused packages, and run verification gates.…
git-project
GitHub Projects (v2) setup and management via gh CLI + GraphQL: organize a repo's issues into epics with native sub-issues, drive a board Status flow (Todo -> In Progress -> Done), set Project Priority, classify with native issue Types (Task/Bug/Feature) instead of labels, scope work with milestones (incl. resolving…
git-ci
CI/CD status queries for GitHub Actions (gh) and GitLab CI (glab). Check pipeline status, failing jobs, workflow runs, job logs, and merge readiness. Use when checking CI status, debugging build failures, viewing job logs, watching pipeline progress, or configuring gh/glab CI read-only allowlists. Not for PR workflows…