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 d-o-hub/github-template-ai-agents --skill code-review-assistantgit clone --depth 1 https://github.com/d-o-hub/github-template-ai-agentsWrote 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/d-o-hub/github-template-ai-agents/code-review-assistant)<a href="https://agentmods.dev/skills/d-o-hub/github-template-ai-agents/code-review-assistant"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/code-review-assistant/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/d-o-hub/github-template-ai-agents/code-review-assistant"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/code-review-assistant.svg" alt="Reviewed on agentmods" width="80" 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.00078 | $0.01855 |
| Opus 5.5 | $0.00031 | $0.00742 |
| Sonnet 5.5 | $0.00016 | $0.00371 |
| Haiku 4.5 | $0.00008 | $0.00186 |
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 4d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Assistant
Automated code review with intelligent analysis of changes, quality checks, and actionable feedback generation.
When to Use
- Reviewing pull requests - Analyze diffs and provide feedback
- Change summarization - Generate PR descriptions from code changes
- Quality checks - Style guide compliance, best practices
- Security review - Detect potential security issues in changes
- Code smell detection - Identify bloaters, dispensables, and couplers
- Refactoring guidance - Suggest targeted improvements
- Review automation - Auto-approve simple changes, flag complex ones
- Learning tool - Explain changes for knowledge sharing
Core Workflow
Phase 1: Change Analysis
- Identify modified files - Categorize by type and risk level
- Calculate metrics - Lines changed, complexity delta, test coverage
- Detect patterns - New features, bug fixes, refactoring, dependencies
- Assess risk - Critical paths, public APIs, security-sensitive areas
Phase 2: Quality Assessment
- Style compliance - Check against project style guide
- Best practices - Design patterns, code organization
- Test coverage - Verify tests accompany changes
- Documentation - Check for necessary doc updates
- Security scan - Identify potential vulnerabilities
Phase 3: Feedback Generation
- Summarize changes - High-level description of what changed
- Identify issues - Bugs, anti-patterns, performance concerns
- Suggest improvements - Refactoring opportunities, optimizations
- Highlight positives - Good practices to reinforce
- Generate review comments - Specific, actionable feedback
Code Smells Detection
Bloaters
- Long Method (>30 lines of logic)
- Large Class (>300 lines)
- Long Parameter List (>4 params)
Object-Orientation Abusers
- Switch Statements (replace with polymorphism)
- Temporary Field
- Refused Bequest
Dispensables
What ships with it
4 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.
- 4d ago Changed · +4 lines 06cfa28ac7b9
- 1mo ago First seen · 225 lines · 78 tokens per session scan A 2b4eb87e01ea
code-review-assistant is a skill published in the GitHub repository d-o-hub/github-template-ai-agents (2 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 1,855 once invoked, about $0.0003 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-31.
Other skills, from other repositories
review-pr
Multi-agent PR review with four modes (review, re-review, self-review, address-feedback) - spawns parallel subagents, saves diff to /tmp for context efficiency, supports file exclusion patterns.
Code Standards
This skill should be used when the user asks about "code quality", "file size limits", "function length", "KISS", "DRY", "YAGNI", "SRP", "best practices", "clean code", "cyclomatic complexity", "code review checklist", "refactoring rules", or mentions specific thresholds for lines of code, function sizes, or code…
code-review-guidelines
When asynchronously reviewing peer code before merging into the main branch.
RubyCritic Code Quality Analysis
Analyze Ruby and Rails code quality with RubyCritic. Identifies code smells, complexity issues, and refactoring opportunities. Provides detailed metrics, scores files A-F, compares branches, and prioritizes high-churn problem areas. Use when analyzing Ruby code quality, reviewing PRs, or identifying technical debt.
tuicr
Use tuicr's review CLI to read and add comments in active TUI review sessions, and launch tuicr in cmux, tmux, Zellij, or Herdr when a user needs an interactive review pane.
liveagent-code-review
Review an open GitHub pull request or the current local branch and working tree with parallel, independent reviewers and evidence-based validation. Use when the user asks for code review, invokes the Code Review action from Git Review, or explicitly mentions this skill.