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.
Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add hyhmrright/brooks-lint/plugin install 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/commands/hyhmrright/brooks-lint/brooks-sweep)<a href="https://agentmods.dev/commands/hyhmrright/brooks-lint/brooks-sweep"><img src="https://agentmods.dev/badge/commands/hyhmrright/brooks-lint/brooks-sweep/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/commands/hyhmrright/brooks-lint/brooks-sweep"><img src="https://agentmods.dev/badge/commands/hyhmrright/brooks-lint/brooks-sweep.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.00019 | $0.00078 |
| Opus 5 | $0.00010 | $0.00039 |
| Sonnet 5 | $0.00004 | $0.00016 |
| Haiku 4.5 | $0.00002 | $0.00008 |
Grade A, and why
brooks-sweep 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 10d 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
Read ${CLAUDE_PLUGIN_ROOT}/skills/brooks-sweep/SKILL.md and follow its instructions exactly. If that file cannot be found, locate the brooks-sweep skill's SKILL.md in this plugin and follow it.
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.
- 10d ago First seen · 6 lines · 19 tokens per session scan A d0b4fe53650f
brooks-sweep is a command published in the GitHub repository hyhmrright/brooks-lint (1,462 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 78 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-30.
Other commands, from other repositories
merge
Finish a PR properly: every check green, every review addressed — human and bot — then merge and clean up.
pr
Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.
spec
Spec-first design: a gap-closing interview that produces a complete spec, with a quality controller that blocks until every section is answered and every question resolved.
plan
Turn an approved spec into an implementation plan an engineer with zero context could execute — with a quality controller that blocks placeholders and hollow tasks.
todo
The quality-gated task list: tasks with real descriptions, testable acceptance criteria, and evidence — a task only closes when the controller agrees it is done.
backlog
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.