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/vmkteam/claude-plugins/mr-reviewnpx skills add vmkteam/claude-plugins --skill mr-reviewgit clone --depth 1 https://github.com/vmkteam/claude-pluginsWrote 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/vmkteam/claude-plugins/mr-review)<a href="https://agentmods.dev/skills/vmkteam/claude-plugins/mr-review"><img src="https://agentmods.dev/badge/skills/vmkteam/claude-plugins/mr-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 | $0.00050 | $0.01673 |
| Opus 5 | $0.00025 | $0.00837 |
| Sonnet 5 | $0.00010 | $0.00335 |
| Haiku 4.5 | $0.00005 | $0.00167 |
Grade A, and why
mr-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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MR Review — ревью чужого Merge Request
Полный цикл code review для MR в GitLab: получить diff, проанализировать код, опубликовать замечания как inline threads.
Подключения из .claude/memory/project-index.md и ~/.claude/memory/infra-{group}.md.
Использование
/mr-review 42
/mr-review 42 --focus security
/mr-review 42 --focus performance
Flow
FETCH MR → READ CODE → REVIEW → SUMMARY → ⏸ HITL → PUBLISH
1. FETCH — получить MR
# Детали MR (title, description, author, source/target branch, diff_refs)
pcurl @{gl_profile} 'https://{gl_host}/api/v4/projects/{gl_project_id}/merge_requests/{mr_iid}' -s
# Diff (список изменённых файлов с содержимым)
pcurl @{gl_profile} 'https://{gl_host}/api/v4/projects/{gl_project_id}/merge_requests/{mr_iid}/changes' -s
# Коммиты MR
pcurl @{gl_profile} 'https://{gl_host}/api/v4/projects/{gl_project_id}/merge_requests/{mr_iid}/commits' -s
# Существующие discussions (чтобы не дублировать замечания)
pcurl @{gl_profile} 'https://{gl_host}/api/v4/projects/{gl_project_id}/merge_requests/{mr_iid}/discussions?per_page=100' -s
Извлечь:
diff_refs(base_sha, start_sha, head_sha) — нужны для inline comments- Список изменённых файлов и их diff
- Описание MR и связанную задачу (из title или description)
- Уже существующие замечания (не дублировать)
2. READ CODE — прочитать контекст
Для каждого изменённого файла:
- Прочитать полный файл локально (не только diff) — для понимания контекста
- Если ветка MR доступна локально —
git fetch origin && git checkout {source_branch} - Если нет — читать через API или анализировать diff as-is
Дополнительно:
- Прочитать связанную задачу из YouTrack (если ID в title/description)
- Понять что должен делать MR — сравнить intent с реализацией
3. REVIEW — анализ кода
Запустить /go-review на изменения MR — 6 ревьюеров:
- Common — соответствие задаче, полнота
- Architecture (Dave Cheney) — структура, зависимости
- Code (Rob Pike) — простота, читаемость
- Security (Filippo Valsorda) — уязвимости, authz
- Tests (Mitchell Hashimoto) — покрытие, качество тестов
- Operability (Peter Bourgon) — логирование, метрики, graceful degradation
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 · 175 lines · 50 tokens per session scan A 3996c192920f
mr-review is a skill published in the GitHub repository vmkteam/claude-plugins (7 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 1,673 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…