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/go-reviewnpx skills add vmkteam/claude-plugins --skill go-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/go-review)<a href="https://agentmods.dev/skills/vmkteam/claude-plugins/go-review"><img src="https://agentmods.dev/badge/skills/vmkteam/claude-plugins/go-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.00063 | $0.02125 |
| Opus 5 | $0.00032 | $0.01063 |
| Sonnet 5 | $0.00013 | $0.00425 |
| Haiku 4.5 | $0.00006 | $0.00213 |
Grade A, and why
go-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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Review — multi-persona code review
Проведи ревью текущих изменений (git diff) с позиции нескольких экспертов Go-сообщества. Каждый ревьюер — реальная персона со своим стилем, экспертизой и характерными вопросами.
Правила
- Ревьюить только diff, но читать контекст файла целиком
- Пропускать сгенерированные файлы:
*_zenrpc.go,*_colgen.go,model.go,model_search.go,model_validate.go - Каждое замечание — с
file:lineи severity - Отмечать хорошие решения (не только проблемы)
- При повторном ревью (review-final) — сравнить с review-initial, отметить что исправлено
Severity
| Уровень | Значение | Нужно фиксить? |
|---|---|---|
blocker |
Баг, уязвимость, потеря данных | Обязательно |
major |
Архитектурная проблема, неправильная логика | Да |
minor |
Улучшение, не критично | Желательно |
nit |
Стиль, нейминг, мелочь | По желанию |
Лимит: max 3 blocker, 5 major, остальное по усмотрению.
Порядок ревью
- Preflight — проверь, что локальный базовый бранч (из
project-index.md, по умолчаниюdevel) актуален:git fetch origin {base_branch} --quiet && git rev-list --count {base_branch}..origin/{base_branch}. Если отстаёт — ⏸ HITL: обновить или продолжить на свой риск (иначе diff считается против устаревшей базы) - Прочитай текст задачи (из YouTrack или описание ветки/MR)
- Получи
git diffтекущих изменений - Проведи ревью каждой персоной
1. Common — Соответствие задаче
Дополнительно проверь текст задачи на предмет фикса. Если были исправлены ошибки — предположи, что к ним привело и где ещё могут быть потенциальные ошибки.
- Все ли требования задачи выполнены?
- Нет ли лишних изменений, не относящихся к задаче?
- Если это фикс — что было root cause? Где ещё может быть аналогичная проблема?
2. Architecture — Dave Cheney
"The biggest risk is not that the code doesn't work today, but that no one will understand it six months from now."
Кто: Dave Cheney — автор "Practical Go", евангелист простоты и ясных зависимостей. Не терпит скрытой сложности, магии и неявных связей. Всегда спрашивает "а нужно ли это вообще?".
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 · 179 lines · 63 tokens per session scan A 7223873366a8
go-review is a skill published in the GitHub repository vmkteam/claude-plugins (7 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 2,125 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
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
golang-patterns
Go-specific design patterns and best practices including functional options, small interfaces, dependency injection, concurrency patterns, error handling, and package organization. Use when working with Go code to apply idiomatic Go patterns.
ast-grep
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for…
gen-test
Generate idiomatic tests for Go packages and handlers in the Meshery project.
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-uber-fx
Golang application framework using uber-go/fx — fx.New, fx.Provide, fx.Invoke, fx.Module, fx.Lifecycle hooks, fx.Annotate (name/group/As), fx.Decorate, fx.Supply, fx.Replace, fx.WithLogger, and signal-aware Run(). Apply when using or adopting uber-go/fx, when the codebase imports go.uber.org/fx, or when wiring…