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/bestdeejay-design/agent-skills/code-reviewnpx skills add bestdeejay-design/agent-skills --skill code-reviewgit clone --depth 1 https://github.com/bestdeejay-design/agent-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/bestdeejay-design/agent-skills/code-review)<a href="https://agentmods.dev/skills/bestdeejay-design/agent-skills/code-review"><img src="https://agentmods.dev/badge/skills/bestdeejay-design/agent-skills/code-review.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.1 | $0.00159 | $0.01782 |
| Opus 5 | $0.00079 | $0.00891 |
| Sonnet 5 | $0.00032 | $0.00356 |
| Haiku 4.5 | $0.00016 | $0.00178 |
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 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Структурированный ревью PR/diff за один запуск: чек-лист, severity, файл:строка, исправление.
Загружай этот скилл когда нужно проверить код (diff, PR, commit) и получить структурированные замечания с приоритетами. Скилл читает изменения, применяет чек-лист из шести категорий и выдаёт готовый текст для комментария в PR.
🎯 When to use
Use this skill when:
- Нужно ревью PR/commit/diff перед мержем
- Просят «проверь код», «найди баги», «замечания по коду»
- Нужен чек-лист code quality перед релизом
- Нужно быстро прогнать diff по категориям: correctness, security, performance, style, tests, edge cases, a11y
- Нужен структурированный комментарий к PR с severity и ссылками на файл:строку
Do NOT use when:
- Нужно внести правки — скилл только анализирует и комментирует; исправления вносит агент отдельно по явному запросу
- Нужен полный аудит всего репозитория, а не изменений — скилл работает по diff
- Нужен security-аудит с PoC-доказательством уязвимости — используй специализированный security-скилл
- Это первичное ревью архитектуры без кода — скилл анализирует код, не схемы
📦 What this skill does
Inputs
--repo PATH— git-репозиторий: берётсяgit diff HEAD(staged + unstaged)--file PATH— обычный файл: ревьюится целиком, каждая строка считается добавленной--diff PATH— файл, содержащий git diff- stdin — git diff (по умолчанию,
git diff | review.py)
Outputs
- Список замечаний:
[severity] файл:строка — правило: проблема+ предлагаемое исправление - Сводка по категориям и severity (critical/warning/nit)
- Markdown-отчёт по шаблону
templates/review-template.md— готов для комментария в PR
🔧 How to use
Шаг 1: получить diff
git diff HEAD > /tmp/pr.diff
Шаг 2: запустить ревью
python3 scripts/review.py --diff /tmp/pr.diff
Или напрямую из репозитория:
python3 scripts/review.py --repo /path/to/repo
Или через stdin:
git diff | python3 scripts/review.py
What ships with it
5 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.
- 5d ago First seen · 143 lines · 159 tokens per session scan A a3aac8e6a519
code-review is a skill published in the GitHub repository bestdeejay-design/agent-skills (5 stars, last pushed today), licensed MIT. It adds 159 tokens to every session and 1,782 once invoked, about $0.0008 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
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
content-hash-cache-pattern
Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.
load-github-action-thread
Download retained Codex GitHub Action thread artifacts and load their rollout history into the local Codex app. Use when asked to open, load, import, resume, or inspect a Codex automation thread from a GitHub Actions run or a related GitHub issue or pull request.
skill
Manage local skills - list, add, remove, search, edit, setup wizard.
composio
Route and complete Composio work across Composio For You and Composio Platform. Use when the user mentions Composio; wants an agent to use apps such as Gmail, Slack, GitHub, Notion, Calendar, or Linear; needs first-time setup, an SDK or MCP integration, CLI operation, migration guidance, current documentation, or help…
minimal-code-discipline
YAGNI-ladder coding discipline for writing changes — existence-first, reuse before writing, dependency ladder, shortest correct diff, with non-negotiables that must never be minimized away.