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/apexiq/skillsmith/code_reviewnpx skills add ApexIQ/skillsmith --skill code_reviewgit clone --depth 1 https://github.com/ApexIQ/skillsmithWrote 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/apexiq/skillsmith/code_review)<a href="https://agentmods.dev/skills/apexiq/skillsmith/code_review"><img src="https://agentmods.dev/badge/skills/apexiq/skillsmith/code_review.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 | $0.00027 | $0.00394 |
| Opus 5 | $0.00014 | $0.00197 |
| Sonnet 5 | $0.00005 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
code-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 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.
What it actually says
👁️ Code Review
Philosophy: Code review is not about finding blame. It's about finding bugs before users do.
The Checklist
1. Correctness
- Does the code do what the PR description says?
- Are edge cases handled (empty lists, null values, network errors)?
- Are there any off-by-one errors in loops?
2. Security
- Is user input validated/sanitized?
- Are ownership checks in place for resources?
- Are secrets hardcoded? (They shouldn't be.)
3. Performance
- Any N+1 queries? (Fetching in a loop instead of batch)
- Are large lists paginated?
- Is there unnecessary re-rendering in React components?
4. Readability
- Are variable/function names descriptive?
- Is complex logic explained with comments?
- Is the code DRY (no copy-paste)?
5. Testing
- Are there tests for the new code?
- Do the tests cover the happy path AND error cases?
Examples
- Good PR: Small, focused, with tests and a clear description.
- Bad PR: 500+ lines, touches unrelated files, no tests.
Guidelines
- Review in <30 mins. If PR is too large, ask to split it.
- Be kind. "Consider using X" is better than "This is wrong."
- If unsure, ask questions instead of blocking.
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 · 51 lines · 27 tokens per session scan A a5be465fb823
code-review is a skill published in the GitHub repository ApexIQ/skillsmith (5 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 394 once invoked, about $0.0001 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
release
Autonomously cut a Rove (@sma1lboy/rove) release end-to-end — detect the semver bump from pending changesets (flagging an upstream minor you didn't intend), run the release gates, bump/tag/push via scripts/release.sh, then poll the GitHub Actions Release workflow with gh until npm publish completes, diagnosing CI…
hyperframes-cli
HyperFrames CLI dev loop. Use when running npx hyperframes init, add, catalog, capture, lint, validate, inspect, layout, snapshot, preview, play, render, publish, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, or remove-background, or when troubleshooting the…
changelog-generator
Draft Rove release notes as Changesets. Writes user-facing entries as .changeset/.md files for @sma1lboy/rove (consumed into packages/kobe/CHANGELOG.md at release time). Use when the user asks for "changelog", "release notes", "what changed", "add a changeset", or before cutting a version. Enforces Rove's no-soft-wrap…
pstack
Rigorous engineering mode for nontrivial work in this repo — a set of named principles plus the leaf skills that apply them. Use when the user says "pstack", "go deep", "be rigorous", "认真做", or when a task involves architecture, a real bug, a refactor, or anything the user will not be watching. Ported from…
xlsx
Extract data from Excel and CSV files.
oad/release
EvoFlux workflow for version bumps, release PRs, GitHub releases, and release notes.