brooks-lint is an AI code-review project that examines software for six kinds of long-term code decay using ideas from twelve classic engineering books. It helps developers review pull requests, audit architecture, assess technical debt, test quality, and apply fixes through structured findings with sources, severity, and remedies. Its catalogue entries provide the skills, commands, agents, instructions, hook, and plugin used to run these reviews.
Borrowing it
Nothing to install: this file belongs to hyhmrright/brooks-lint. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hyhmrright/brooks-lint/main/CLAUDE.mdgit clone --depth 1 https://github.com/hyhmrright/brooks-lintWrote 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/instructions/hyhmrright/brooks-lint/claude-md)<a href="https://agentmods.dev/instructions/hyhmrright/brooks-lint/claude-md"><img src="https://agentmods.dev/badge/instructions/hyhmrright/brooks-lint/claude-md/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/instructions/hyhmrright/brooks-lint/claude-md"><img src="https://agentmods.dev/badge/instructions/hyhmrright/brooks-lint/claude-md.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.03025 | $0.03025 |
| Opus 5 | $0.01512 | $0.01512 |
| Sonnet 5 | $0.00605 | $0.00605 |
| Haiku 4.5 | $0.00302 | $0.00302 |
Grade A, and why
brooks-lint CLAUDE.md 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 6d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code when modifying this repository. For repo layout, install steps, and user-facing usage, see README.md — this file covers only what's needed to safely change the repo.
What This Repo Is
brooks-lint is a Claude Code Plugin for code-quality diagnosis grounded in twelve classic software engineering books. Six independent skills under skills/ (PR Review, Architecture Audit, Tech Debt, Test Quality, Health Dashboard, Full Sweep) each produce findings in the Iron Law form: Symptom → Source → Consequence → Remedy.
Harness: brooks-lint maintenance
Goal: drive changes to brooks-lint itself through a verified pipeline so manifests, evals, docs, and trigger boundaries never drift.
Trigger: when working ON the plugin — add/edit a skill or guide, refresh the eval suite, fix trigger descriptions, or cut a release — use the brooks-harness skill. It runs a sequential subagent pipeline (.claude/agents/): skill-author → eval-curator → consistency-qa → trigger-boundary-auditor → release-manager. Simple questions, or using the analysis skills on some target codebase, do not trigger it.
Change history:
| Date | Change | Target | Reason |
|---|---|---|---|
| 2026-06-01 | Initial harness: 5-stage pipeline orchestrator + 4 new agents (skill-author, eval-curator, consistency-qa, release-manager), reusing trigger-boundary-auditor | .claude/agents/, .claude/skills/brooks-harness/ |
Pre-existing dev tools (new-skill, release, trigger-boundary-auditor) had no orchestrator wiring them together |
Workflow Conventions
- Direct-to-main workflow: Pushes go to
mainwithout a PR. After Edit/Write, the global rule'sagent-skills:code-simplify+agent-skills:reviewsteps still run before commit; only the optional PR-onlycode-review:code-reviewstep is skipped. - Doc sources of truth:
package.jsonis canonical for version; book inventory is canonical inskills/_shared/source-coverage.md(see Gotchas for derivation). README.md, AGENTS.md, GEMINI.md, and CHANGELOG.md must stay in sync —npm run validateenforces this. - VS Code extension is OUT OF SCOPE. Do not plan, propose, or reference VS Code extension features.
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.
- 6d ago Changed · +101 tokens per session ebfaadbaf533
- 9d ago First seen · 91 lines · 2,924 tokens per session scan A 9f9e565188de
brooks-lint CLAUDE.md is an instructions file published in the GitHub repository hyhmrright/brooks-lint (1,456 stars, last pushed yesterday), licensed MIT. It adds 3,025 tokens to every session, about $0.0151 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.