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
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.
git 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/plugins/hyhmrright/brooks-lint/gemini-extension)<a href="https://agentmods.dev/plugins/hyhmrright/brooks-lint/gemini-extension"><img src="https://agentmods.dev/badge/plugins/hyhmrright/brooks-lint/gemini-extension/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/plugins/hyhmrright/brooks-lint/gemini-extension"><img src="https://agentmods.dev/badge/plugins/hyhmrright/brooks-lint/gemini-extension.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
brooks-lint 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 today.
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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "brooks-lint",
"version": "1.5.0",
"description": "AI code reviews grounded in twelve classic engineering books — decay risk diagnostics with book citations, severity labels, and six analysis modes (PR review, architecture audit, tech debt, test quality, health dashboard, full-sweep auto-fix)",
"author": "hyhmrright",
"license": "MIT",
"repository": {
"type": "git",
"url": "https://github.com/hyhmrright/brooks-lint.git"
},
"engines": {
"gemini": ">=0.30.0"
},
"contribution": {
"skills": [
{
"id": "brooks-review",
"path": "skills/brooks-review"
},
{
"id": "brooks-audit",
"path": "skills/brooks-audit"
},
{
"id": "brooks-debt",
"path": "skills/brooks-debt"
},
{
"id": "brooks-test",
"path": "skills/brooks-test"
},
{
"id": "brooks-health",
"path": "skills/brooks-health"
},
{
"id": "brooks-sweep",
"path": "skills/brooks-sweep"
}
],
"commands": [
{
"id": "brooks-review",
"description": "PR-level code review across six decay risk dimensions",
"path": "commands/brooks-review.md"
},
{
"id": "brooks-audit",
"description": "Full architecture audit with module dependency map",
"path": "commands/brooks-audit.md"
},
{
"id": "brooks-debt",
"description": "Tech debt classification ranked by Pain × Spread",
"path": "commands/brooks-debt.md"
},
{
"id": "brooks-test",
"description": "Test suite health review across six test decay risks",
"path": "commands/brooks-test.md"
},
{
"id": "brooks-health",
"description": "Combined health dashboard aggregating all four quality dimensions (PR review, architecture, tech debt, test quality) into a single weighted score",
"path": "commands/brooks-health.md"
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.
- today First seen · 75 lines scan A 471973ca072f
brooks-lint is a plugin published in the GitHub repository hyhmrright/brooks-lint (1,456 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-08.
Other plugins, from other repositories
logic-lens
Logic-first code review using semi-formal execution tracing. Surfaces behavioral bugs, semantic errors, and runtime failures that linters miss.
craftsman
Ship something with Lovable, Replit, Bolt, v0, Claude Code, or Codex and it works, but nobody with an engineering background has checked it. This is the engineering review you'd get from the technical co-founder you don't have. craft-audit checks the whole project across ten areas: UX, frontend, backend, database…
omen-development
Code analysis skills for active development: find bugs, assess impact, plan refactoring, audit architecture, and more.
ai-architect-mcp-codebase
Rust MCP server that indexes ANY codebase into a LadybugDB property graph — source in 11 languages with full AST, plus docs/config/binaries as File nodes (.js→Imports, Markdown→References). Resolves imports and call chains, detects communities via Leiden, traces execution flows from entry points, and exposes 26 MCP…
slopmop marketplace
Slop-mop quality gates as a Claude skill — directed remediation for AI-assisted codebases.
cpp-lsp
Claude Code plugin for C/C++ development with clangd LSP integration, 14 automated hooks for compilation, linting (clang-tidy), formatting (clang-format), and memory analysis (valgrind).