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/dgouron/review-flow/clean-codenpx skills add DGouron/review-flow --skill clean-codegit clone --depth 1 https://github.com/DGouron/review-flowWhat 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.00084 | $0.03097 |
| Opus 5 | $0.00042 | $0.01548 |
| Sonnet 5 | $0.00017 | $0.00619 |
| Haiku 4.5 | $0.00008 | $0.00310 |
Grade A, and why
clean-code 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 2d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Code — Refactor & Challenge
Source: Clean Code (Robert C. Martin, 2008) + Clean Coder (2011).
When to activate
- REFACTOR phase of the TDD cycle (after GREEN, before the next RED)
- Implementation self-review (end of
feature-implementerworkflow) - Code review of a PR/MR
- Explicit request for simplification, readability, "challenge this code"
Scope vs neighboring skills
This skill NEVER duplicates the content of /solid or /anti-overengineering. It complements them.
| Concern | Skill to use |
|---|---|
| Responsibility architecture (SRP, OCP, LSP, ISP, DIP) | /solid |
| Should I add a pattern? (YAGNI, KISS, pragmatic architecture) | /anti-overengineering |
| Readability, naming, functions, smells, refactor heuristics | /clean-code (here) |
Once the pattern is decided (/anti-overengineering) and responsibilities are placed (/solid), /clean-code makes intent self-evident.
The 5 pillars
1. SOLID Design — delegated to /solid
Activate /solid for SRP, OCP, LSP, ISP, DIP. Mentioned here only as a structuring reminder: clean code rests on well-placed responsibilities.
2. Readability first
"The ratio of time spent reading to writing code is well over 10:1. We are constantly reading old code as part of the effort to write new code." — Robert C. Martin
Naming (chap. 2)
- Intention-revealing: the name should be enough to understand. If you write a comment to explain, the name is broken.
- OK
daysSinceLastReview— KOd,days,elapsed - OK
filterMergedPullRequests(prs)— KOprocessPrs(prs, true)
- OK
- No disinformation:
accountListmust be aList, otherwiseaccounts. - Perceptible distinction:
getActiveAccount()vsgetActiveAccounts()is a time bomb. PrefergetCurrentAccount()vsgetAllActiveAccounts(). - Searchable: short names only for short scopes (loop index =
indexin a 3-line loop — notieven though short). - No encoding: no Hungarian notation (
strName,bIsActive), noIprefix for interfaces. - Class names = nouns (
ReviewContext,ThreadFetchGateway), method names = verbs (save,fetchByCriteria). - Full words only (project rule,
coding-standards.md): noex,i,ctx,gw. Alwaysexisting,index,context,gateway.
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.
- 2d ago First seen · 210 lines · 84 tokens per session scan A 55b1b878cb47
clean-code is a skill published in the GitHub repository DGouron/review-flow (42 stars, last pushed 18d ago), licensed MIT. It adds 84 tokens to every session and 3,097 once invoked, about $0.0004 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
industry-chain
产业链下钻与不可替代性判定方法:以龙头为"需求入口"沿供应链逐层下钻(整机 / 龙头 → 部件 → 核心器件 → 材料 → 衬底与设备),用物理 / 材料约束(扩产周期、良率、认证周期、有无替代)当筛子找供给刚性的卡口;给每个标的贴不可替代性标签(techmoat / capacitymoat / both / 待补)并列证据;含"卡口越硬越贵"与预期差四问的校准。当任务涉及产业链位置、上下游、护城河、不可替代性、供给瓶颈、竞争格局时加载;单纯取数、估值计算、财报拆分等不涉及产业链结构的任务不要加载。只产出框架与证据表,不给投资动作建议。.
selecting-vizro-charts
Use this skill when choosing chart types, applying Plotly Express conventions, configuring colors, building KPI cards, or adding tables (AG Grid) to Vizro dashboards. Activate when the user asks which chart fits their data, needs custom chart functions, wants to set colors or palettes, is creating KPI metric cards, or…
verify-changes
Verify a code change in this repo before committing or opening a PR. Use after editing collector (backend), web (frontend), shared package, or the Go agent — picks the minimal sufficient check set per touched area.
openai-docs
Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations (for example: Codex, Responses API, Chat Completions, Apps SDK, Agents SDK, Realtime, model capabilities or limits); prioritize OpenAI docs MCP tools and restrict any fallback browsing to…
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…