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/alexmond/jhelm/code-reviewernpx skills add alexmond/jhelm --skill code-reviewergit clone --depth 1 https://github.com/alexmond/jhelmWhat 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.00782 |
| Opus 5 | $0.00032 | $0.00391 |
| Sonnet 5 | $0.00013 | $0.00156 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
code-reviewer 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 3d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer
Automated code review tools for analyzing pull requests, detecting code quality issues, and generating review reports.
Adapted from alirezarezvani/claude-skills with Java support added.
Tools
PR Analyzer
Analyzes git diff between branches to assess review complexity and identify risks.
python3 $CLAUDE_SKILL_DIR/scripts/pr_analyzer.py /path/to/repo
python3 $CLAUDE_SKILL_DIR/scripts/pr_analyzer.py . --base main --head feature-branch
python3 $CLAUDE_SKILL_DIR/scripts/pr_analyzer.py /path/to/repo --json
Detects: Hardcoded secrets, SQL injection patterns, debug statements, TODO/FIXME, System.out.println in Java
Code Quality Checker
Analyzes source code for structural issues, code smells, and SOLID violations.
python3 $CLAUDE_SKILL_DIR/scripts/code_quality_checker.py /path/to/code
python3 $CLAUDE_SKILL_DIR/scripts/code_quality_checker.py . --language java
python3 $CLAUDE_SKILL_DIR/scripts/code_quality_checker.py /path/to/code --json
Detects: Long functions (>50 lines), large files (>500 lines), god classes (>20 methods), deep nesting (>4 levels), too many parameters (>5), high cyclomatic complexity
Review Report Generator
Combines PR analysis and code quality findings into structured review reports.
python3 $CLAUDE_SKILL_DIR/scripts/review_report_generator.py /path/to/repo
python3 $CLAUDE_SKILL_DIR/scripts/review_report_generator.py . --format markdown --output review.md
Verdicts:
| Score | Verdict |
|---|---|
| 90+ with no high issues | Approve |
| 75+ with ≤2 high issues | Approve with suggestions |
| 50-74 | Request changes |
| <50 or critical issues | Block |
Reference Guides
references/code_review_checklist.md— Systematic checklists (pre-review, correctness, security, performance, maintainability, testing)references/coding_standards.md— Language-specific standardsreferences/common_antipatterns.md— Antipattern catalog with examples and fixes
What ships with it
6 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.
- 3d ago First seen · 80 lines · 63 tokens per session scan A 78eae07b04b1
code-reviewer is a skill published in the GitHub repository alexmond/jhelm (4 stars, last pushed 9d ago), licensed Apache-2.0. It adds 63 tokens to every session and 782 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
evergreen
Evergreen CI infrastructure, configuration validation. Use when modifying .evergreen/ config, preparing to submit changes or understanding the Evergreen test matrix.
sync-agents-docs
Sync AGENTS.md files, skills, and references after buildSrc or convention changes. Use after modifying build plugins, formatting rules, testing conventions, or task names to keep documentation consistent.
dependabot-batch
Use when reviewing Radar's weekly Dependabot PRs and replacing the safe, 72-hour-soaked updates with one changelog-vetted, tested PR.
test-radar
Use when building and testing Radar changes with the repository's real-instance smoke-test workflow.
visual-test
Use when visually testing Radar UI changes against a real Kubernetes cluster with Playwright screenshots.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.