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.
npx skills add hyhmrright/brooks-lint --skill releasegit 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/skills/hyhmrright/brooks-lint/release)<a href="https://agentmods.dev/skills/hyhmrright/brooks-lint/release"><img src="https://agentmods.dev/badge/skills/hyhmrright/brooks-lint/release.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00135 | $0.00722 |
| Opus 5 | $0.00068 | $0.00361 |
| Sonnet 5 | $0.00027 | $0.00144 |
| Haiku 4.5 | $0.00014 | $0.00072 |
Grade A, and why
release 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 8d 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
brooks-lint — Release
Target version comes from $ARGUMENTS (e.g. 1.4.0). If empty, ask the maintainer
for the semver bump before doing anything.
Execute these steps in order. bump-version.mjs reads the version FROM
package.json and does NOT touch the changelog — so the version edit and the
CHANGELOG entry are manual; the script only fans the version out to the manifests
and every version-bearing text file.
- Set the source of truth.
npm version <version> --no-git-tag-version(the--no-git-tag-versionflag is required — plainnpm versionwould create its own commit + tag and collide with the manual commit in step 5). - Propagate.
npm run bump— writes the version into.claude-plugin/plugin.json,.claude-plugin/marketplace.json,.codex-plugin/plugin.json,gemini-extension.json, and every version-bearing text file discovered byscripts/version-refs.mjs(all six README badges plus the JSON-LDsoftwareVersionon the docs landing page). Do not maintain a list here — the script's is authoritative. - Write the changelog. Add a new section at the top of
CHANGELOG.mdwith categorized notes (Added / Fixed / Changed) summarizing the commits since the last release tag (git log <last-tag>..HEAD --oneline). The heading MUST be## [<version>] - YYYY-MM-DD—npm run validateparses that exact shape and fails on a bare## <version>. - Validate.
npm run validate— fails if any manifest, any version-bearing text file, or the CHANGELOG entry is out of sync. Fix and re-run until clean. Thennpm test. - Commit & push. Stage everything
npm run bumprewrote plusCHANGELOG.md— readgit statusrather than naming files, because the version-bearing set is discovered from disk and is more than one README; commit with a conventional message (chore(release): bump version to <version>); push tomain(direct-to-main repo — no PR). - Tag & publish. Create the GitHub release:
gh release create v<version> --title "v<version>" --notes "<changelog section>".
Report the released version and the GitHub release URL when done.
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.
- 8d ago First seen · 52 lines · 135 tokens per session scan A 9f98f4046fe2
release is a skill published in the GitHub repository hyhmrright/brooks-lint (1,455 stars, last pushed 6d ago), licensed MIT. It adds 135 tokens to every session and 722 once invoked, about $0.0007 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
bump-version
Bump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README badge), then validate. Use when cutting a release or when npm run validate reports a version mismatch.
release-docs
Diff-driven documentation sync after a release. Determines what source files changed, delegates changelog to zuvo:docs, updates only docs whose source changed. Flags: --dry-run, explicit range argument.
publish
Use when the user invokes /evo:publish or asks to release a new version, ship a release, or publish a tag. Wraps the go-native self-healing release pipeline (evolve release) — pre-flight checks, auto-changelog, atomic ship, marketplace propagation poll, auto-rollback on failure.
release
Use when the user asks whether a release is ready, or to gate/verify release criteria before publishing. A thin readiness-gate that runs the existing read-only verifiers (evolve release-preflight, evolve release-consistency), adds the CI-green-on-main and no-WIP-commit checks they don't cover, then delegates execution…
verify-release
Use when the user invokes /evo:verify-release or asks to check whether a release has propagated, whether the marketplace is up to date, or whether installed plugins reflect the latest version. Wraps legacy/scripts/release/marketplace-poll.sh for standalone post-publish verification.
changelog
Add CHANGELOG.md entries, derive them from commits, or cut a Keep a Changelog and SemVer release.