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 adityasasidhar/claude-code-in-100-lines --skill code-reviewgit clone --depth 1 https://github.com/adityasasidhar/claude-code-in-100-linesWrote 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/adityasasidhar/claude-code-in-100-lines/code-review)<a href="https://agentmods.dev/skills/adityasasidhar/claude-code-in-100-lines/code-review"><img src="https://agentmods.dev/badge/skills/adityasasidhar/claude-code-in-100-lines/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.1 | $0.00023 | $0.00307 |
| Opus 5 | $0.00012 | $0.00153 |
| Sonnet 5 | $0.00005 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00031 |
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 8d 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
Use this when asked to review code, a diff, or a PR.
Before you start
- Get the diff:
git diff,git diff main...HEAD, orgit show <sha>. - Read enough surrounding code to understand intent. A line is only wrong relative to what it is supposed to do.
What to look for, in priority order
- Correctness — logic errors, off-by-one, wrong operator, inverted conditions, unhandled None/null, race conditions, resource leaks.
- Edge cases — empty input, zero, negative, very large input, concurrent access, partial failure.
- Security — injection (shell, SQL), unvalidated input, secrets in code, unsafe deserialization.
- Error handling — swallowed exceptions, missing cleanup, errors that never surface.
- Quality — duplication that should be reused, dead code, misleading names, needless complexity.
How to report
- Lead with the most serious issue. Bugs before style.
- For each finding:
file:line, what is wrong, why it matters, and the fix. - Distinguish "this is a bug" from "I would prefer". Do not inflate nits into blockers.
- If the diff is clean, say so plainly — do not manufacture findings.
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.
- 8d ago First seen · 26 lines · 23 tokens per session scan A 215a7fa446de
code-review is a skill published in the GitHub repository adityasasidhar/claude-code-in-100-lines (2 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 307 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
md-audit
Read-only code quality audit — scan the current working directory for common issues (bugs, dead code, security hotspots, missing error handling) and return a prioritised findings report. No files are edited. Use when asked to "audit the code", "quick audit", "find issues", "code scan", or "what's wrong with this…
comet-verify
Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.
comet-review
A read-only review guide for checking the current Comet change, a managed software-change workflow. It focuses on correctness, security, and boundary problems without changing files or advancing the workflow.
claude_code_delegation
Delegate coding, review, and refactor tasks to Claude Code CLI through Row-Bot's approval-gated shell workflow.
comet-github-pr-review
A read-only review process for pull requests in Comet's GitHub repositories. A pull request is a proposed code change; the review checks its current code, related issue, comments, merge status, and automated checks.
developer_pr_prep
Prepare branches, diffs, tests, and GitHub PR text from Developer Studio.