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 hubertlim/SkillForge --skill code-review-checklistgit clone --depth 1 https://github.com/hubertlim/SkillForgeWrote 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/hubertlim/skillforge/code-review-checklist)<a href="https://agentmods.dev/skills/hubertlim/skillforge/code-review-checklist"><img src="https://agentmods.dev/badge/skills/hubertlim/skillforge/code-review-checklist/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/hubertlim/skillforge/code-review-checklist"><img src="https://agentmods.dev/badge/skills/hubertlim/skillforge/code-review-checklist.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.00014 | $0.00239 |
| Opus 5.5 | $0.00006 | $0.00096 |
| Sonnet 5.5 | $0.00003 | $0.00048 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
code-review-checklist 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 1mo 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.
What it actually says
Step 1: Understand Context
Read the PR description and linked issues
- Understand what problem this change solves
- Check if the approach matches the agreed design
- Note the scope of changes
Step 2: Security Review
Check for security vulnerabilities
- Look for injection vulnerabilities (SQL, XSS, command)
- Verify authentication and authorization checks
- Ensure no secrets or keys are hardcoded
- Validate all user inputs are sanitized
Step 3: Logic and Correctness
Verify the code does what it claims
- Trace the happy path end to end
- Check edge cases and error handling
- Look for off-by-one errors and null checks
Step 4: Readability
Ensure the code is maintainable
- Check naming clarity for variables and functions
- Verify comments explain why, not what
- Look for unnecessary complexity
Step 5: Test Coverage
Validate test quality
- Check that new code has corresponding tests
- Verify edge cases are tested
- Ensure tests are deterministic
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.
- 1mo ago First seen · 46 lines · 14 tokens per session scan A 91fc3c93a039
code-review-checklist is a skill published in the GitHub repository hubertlim/SkillForge (5 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 239 once invoked, about $0.0001 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
open-code-review
Performs AI-powered code review on Git changes using the ocr CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply…
cn-check
Install and run the Continue CLI (cn) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
learn-from-sage
Detection-gap (miss) analysis for Code Review Sage. Learn from shipped fixes, acted-on human comments, and design outcomes to close reviewer blind spots. Inline during review stages a candidate; a human triggers a one-shot AI consolidation into the live ruleset.
git
Git and code hosting platform management — GitHub, GitLab, Codeberg, Forgejo. Zero barrier — install x-cmd and manage repos from the terminal. Use for "git", "github", "gitlab", "repo", "pull request", "code hosting".
review
Comprehensive security and correctness audit. Use for review, deep review, thermo nuclear, or thermonuclear requests and branch or PR diff audits.
meta-codereview-current-diff
Read the current uncommitted diff, run three independent reviewers (safety + tests-coverage + style) in parallel, then arbitrate a single BLOCK / BLOCKWITHOVERRIDE / PASSWITHNOTES verdict. Use before commit when you want a multi-perspective second-opinion instead of a single-reviewer agent loop.