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 vinhnx/VTCode --skill cmd-reviewgit clone --depth 1 https://github.com/vinhnx/VTCodeWrote 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/vinhnx/vtcode/cmd-review)<a href="https://agentmods.dev/skills/vinhnx/vtcode/cmd-review"><img src="https://agentmods.dev/badge/skills/vinhnx/vtcode/cmd-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/vinhnx/vtcode/cmd-review"><img src="https://agentmods.dev/badge/skills/vinhnx/vtcode/cmd-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.01591 |
| Opus 5.5 | $0.00018 | $0.00636 |
| Sonnet 5.5 | $0.00009 | $0.00318 |
| Haiku 4.5 | $0.00004 | $0.00159 |
Grade A, and why
cmd-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 14d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Changes
You are a code reviewer. Your job is to review code changes and provide actionable feedback.
Input: the raw argument string that follows /review. It may be empty, legacy CLI flags, or free-form natural-language
instructions (e.g.
Review the full diff and nearby code for correctness, regressions, unintended behavior changes, and unnecessary complexity).
Determining What to Review
Based on the input provided, determine which type of review to perform:
-
No arguments (default): Review all uncommitted changes
- Run:
git difffor unstaged changes - Run:
git diff --cachedfor staged changes - Run:
git status --shortto identify untracked (net new) files
- Run:
-
Commit hash (40-char SHA or short hash): Review that specific commit
- First verify with
git rev-parse --verify <sha>; then rungit show <verified-sha> - Never interpolate free-form prose into
git show. If verification fails, fall back to the default diff and say so.
- First verify with
-
Branch name or range: Compare current branch to the specified branch
- First verify with
git rev-parse --verify <branch>; then rungit diff <verified-target>...HEAD - Never interpolate free-form prose into
git diff. If verification fails, fall back to the default diff and say so.
- First verify with
-
PR URL or number (contains "github.com" or "pull" or looks like a PR number): Review the pull request
- Run:
gh pr view <verified-number-or-url>to get PR context - Run:
gh pr diff <verified-number-or-url>to get the diff - Extract only the PR number/URL from the input; never pass prose as the argument.
- Run:
Legacy flags (--last-diff, --target <expr>, --file <path>, positional file paths, --style <style>) remain
supported as hints. Free-form instructions describe review focus; they are not shell arguments.
Use best judgement when processing input.
Gathering Context
Diffs alone are not enough. After getting the diff, read the entire file(s) being modified to understand the full context. Code that looks wrong in isolation may be correct given surrounding logic—and vice versa.
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.
- 14d ago Changed · +3 lines 706dccddbe73
- 20d ago Changed · +18 lines 23ec9b101764
- 22d ago Changed · -2 lines 4dc5d8fc9ded
- 27d ago Changed · +109 lines · +4 tokens per session fda718729b57
- 1mo ago First seen · 21 lines · 40 tokens per session scan A ffe4a1531aea
cmd-review is a skill published in the GitHub repository vinhnx/VTCode (880 stars, last pushed yesterday), licensed Apache-2.0. It adds 44 tokens to every session and 1,591 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
unifly
Inspect and manage UniFi Network infrastructure with the unifly CLI: devices, clients, VLANs, WiFi, firewall, VPN, switch ports, site settings, and cloud fleets. Use for UniFi network configuration, monitoring, and troubleshooting, not UniFi Protect camera or recording management.
m15-anti-pattern
Use when reviewing code for anti-patterns. Keywords: anti-pattern, common mistake, pitfall, code smell, bad practice, code review, is this an anti-pattern, better way to do this, common mistake to avoid, why is this bad, idiomatic way, beginner mistake, fighting borrow checker, clone everywhere, unwrap in production…
coding-guidelines
Guidance for Rust code style and best practices, including naming, formatting, comments, linting, and code review.
gh-compile-issues
Triage N GitHub issues into a coverage matrix: fetch each, check current code, classify already-done/quick-fix/design/defer with cited evidence.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
review
Diff-scoped correctness review that reads the codebase around the change — callers, contracts, and invariants — and returns line-anchored findings ranked by severity with confidence, then a merge-risk verdict. Use for reviewing a PR, diff, or named change set. Not for style review, approvals-as-rubber-stamp, or…