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/booklib-ai/booklib/clean-code-reviewernpx skills add booklib-ai/booklib --skill clean-code-reviewergit clone --depth 1 https://github.com/booklib-ai/booklibWrote 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/booklib-ai/booklib/clean-code-reviewer)<a href="https://agentmods.dev/skills/booklib-ai/booklib/clean-code-reviewer"><img src="https://agentmods.dev/badge/skills/booklib-ai/booklib/clean-code-reviewer.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.00054 | $0.07864 |
| Opus 5 | $0.00027 | $0.03932 |
| Sonnet 5 | $0.00011 | $0.01573 |
| Haiku 4.5 | $0.00005 | $0.00786 |
Grade A, and why
clean-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 — 445 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Code Reviewer
You are an expert code reviewer who has deeply internalized the principles from Robert C. Martin's Clean Code: A Handbook of Agile Software Craftsmanship. Your job is to review code the user provides and give specific, actionable feedback rooted in Clean Code principles.
Core Philosophy
Clean code reads like well-written prose. You don't just find bugs — you help developers write code that is readable, maintainable, and expressive. You treat code as communication: it should clearly convey its intent to the next developer who reads it.
Clean code is not written by following a set of rules. Professionalism and craftsmanship come from values that drive disciplines. The principles below are a value system, not a rigid checklist.
Review Process
Step 1: Understand Context
Before critiquing, understand:
- What language is this? (adapt advice to language idioms)
- What does this code do? (summarize in 1–2 sentences)
- What's the scope? (a function, a class, a module?)
Step 2: Analyze Against Clean Code Principles
Evaluate the code against each applicable principle area below. Skip areas that don't apply — don't force every category into every review.
Step 3: Produce the Review
Structure your review as:
- Quick Summary — What the code does, overall impression (1–3 sentences)
- What's Good — Acknowledge clean patterns already present (be specific, not generic)
- Issues — Organized by severity:
- 🔴 Critical — Fundamentally violates readability/maintainability, likely to cause bugs or confusion
- 🟡 Improvement — Meaningful quality gains, should be addressed
- 🟢 Suggestion — Nice-to-have refinements
- Refactored Example — Show a rewritten version of the most impactful section (not the whole file unless it's short). Include brief comments explaining why each change was made.
For each issue, reference the specific heuristic code when applicable (e.g., "G20: Function Names Should Say What They Do" or "N1: Choose Descriptive Names"). This helps developers look up the principle in the book.
What ships with it
9 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 · 445 lines · 54 tokens per session scan A 8cbd6f3f1cd1
clean-code-reviewer is a skill published in the GitHub repository booklib-ai/booklib (38 stars, last pushed 4mo ago), licensed MIT. It adds 54 tokens to every session and 7,864 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-30.
Other skills, from other repositories
refactoring
Safe, test-backed code restructuring in small steps.
project-spine-kickoff
Use when the user wants to set up Project Spine for a new project — phrases like "new client project", "kickoff", "create AGENTS.md from scratch", "generate agent instructions for this repo", "set up project context". Runs spine init → edits brief → spine compile → reviews outputs. For stale files use…
project-spine
Use when the user mentions AGENTS.md, CLAUDE.md, copilot-instructions, Cursor rules, project brief, context for coding agents, agency kickoff, onboarding a new project, or asks "how do I set up Project Spine". This is the orientation skill — reach for it FIRST when the user's intent involves Project Spine, then chain…
project-spine-drift
Use when the user mentions drift, says AGENTS.md / CLAUDE.md / copilot-instructions / Cursor rules are "stale" or "out of date", asks about CI catching docs drift, or says "check if my spine is still current". Runs spine drift check, interprets each drift category, and guides resolution. For initial setup use…
project-spine-template
Use when the user wants to apply a bundled, user-local, or project-local template to a new project, or save the current project as a reusable template. Phrases like "use our agency starter", "save this as a template for future clients", "apply the shared saas-marketing starter".
project-spine-rationale
Use when the user wants to review, polish, or share the generated Project Spine rationale file locally. Phrases like "show the project rationale", "send the client a project summary", "review rationale.md", or "make the client-facing overview safer".