Is Brooks Audit safe and trustworthy?

tashan scores Brooks Audit on public evidence — see the measured signals. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Brooks Audit?

Drop the skill folder into ~/.claude/skills/ (user scope) or .claude/skills/ (project scope).

Who maintains Brooks Audit?

source: hyhmrright/brooks-lint.

‹ The Index

Brooks Audit

skill

Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized, or asks "does this follow clean architecture?" or "why does everything depend on everything?". Also triggers for onboarding requests: "explain this codebase to a new developer" or "give me a codebase tour" (use onboarding mode). Do NOT trigger for: PR-level code review (use brooks-review) or line-level refactoring questions — this skill analyzes structural/module-level concerns, not individual functions.

Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format

Category: Dev Tools & CI — see all ranked ›

Install (Claude Code):

cp -r brooks-audit ~/.claude/skills/

Adoption: 1 repos

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

source ↗ · skill:hyhmrright/brooks-audit

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-05 · scorer s5 · how · something wrong here?