Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ValorVie/custom-skillsnpx agentmods add skills/valorvie/custom-skills/code-review-assistantWrote 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/valorvie/custom-skills/code-review-assistant)<a href="https://agentmods.dev/skills/valorvie/custom-skills/code-review-assistant"><img src="https://agentmods.dev/badge/skills/valorvie/custom-skills/code-review-assistant.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.00064 | $0.01617 |
| Opus 5 | $0.00032 | $0.00809 |
| Sonnet 5 | $0.00013 | $0.00323 |
| Haiku 4.5 | $0.00006 | $0.00162 |
Grade A, and why
code-review-assistant 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Assistant
Language: English | 繁體中文
Version: 1.0.0 Last Updated: 2025-12-24 Applicability: Claude Code Skills
Core Standard: This skill implements Code Review Checklist. For comprehensive methodology documentation, refer to the core standard.
Purpose
This skill provides systematic checklists for code review and pre-commit verification.
Quick Reference
Comment Prefixes
| Prefix | Meaning | Action Required |
|---|---|---|
| ❗ BLOCKING | Must fix before merge | 🔴 Required |
| ⚠️ IMPORTANT | Should fix, but not blocking | 🟡 Recommended |
| 💡 SUGGESTION | Nice-to-have improvement | 🟢 Optional |
| ❓ QUESTION | Need clarification | 🔵 Discuss |
| 📝 NOTE | Informational, no action | ⚪ Informational |
Review Checklist Categories
- Functionality - Does it work?
- Design - Right architecture?
- Quality - Clean code?
- Readability - Easy to understand?
- Tests - Adequate coverage?
- Security - No vulnerabilities?
- Performance - Efficient?
- Errors - Properly handled?
- Docs - Updated?
- Dependencies - Necessary?
Pre-Commit Checklist
- Build succeeds (zero errors, zero warnings)
- All tests pass
- Code follows project standards
- No security vulnerabilities
- Documentation updated
- Branch synced with target
Detailed Guidelines
For complete standards, see:
AI-Optimized Format (Token-Efficient)
For AI assistants, use the YAML format file for reduced token usage:
- Base standard:
ai/standards/code-review.ai.yaml
Example Review Comments
❗ BLOCKING: Potential SQL injection vulnerability here.
Please use parameterized queries instead of string concatenation.
⚠️ IMPORTANT: This method is doing too much (120 lines).
Consider extracting validation logic to a separate method.
💡 SUGGESTION: Consider using a Map here instead of an array for O(1) lookup.
❓ QUESTION: Why are we using setTimeout here instead of async/await?
📝 NOTE: This is a clever solution! Nice use of reduce here.
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.
- 5d ago First seen · 224 lines · 64 tokens per session scan A 9578443b6263
code-review-assistant is a skill published in the GitHub repository ValorVie/custom-skills (5 stars, last pushed 8d ago), licensed MIT. It adds 64 tokens to every session and 1,617 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-09-03.
Other skills, from other repositories
address-conductor-comment
A workflow for handling pending Conductor code-review comments, including reading their discussion and assigning changes to subagents when appropriate.
explain-comment
A skill that reads a specified file or code range and adds explanatory comments in Japanese. The comments use a question style and focus on important logic, design choices, and side effects.
code-review
Analyze diffs, suggest improvements, and review pull requests with actionable feedback.
tech-debt
Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.