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 brain-bootstrap/claude-code-brain-bootstrap --skill lintgit clone --depth 1 https://github.com/brain-bootstrap/claude-code-brain-bootstrapWrote 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/brain-bootstrap/claude-code-brain-bootstrap/lint)<a href="https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/lint"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/lint/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/skills/brain-bootstrap/claude-code-brain-bootstrap/lint"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/lint.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.00030 | $0.00445 |
| Opus 5.5 | $0.00012 | $0.00178 |
| Sonnet 5.5 | $0.00006 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
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 1mo 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
Lint Skill
Run linter and formatter, fix auto-fixable issues.
Protocol
1. Read lint command
Read claude/build.md for the lint and format commands.
2. Run formatter check (non-destructive)
# Example: npx biome check . 2>&1 | tail -30
# Example: black --check . 2>&1 | tail -20
3. Run linter
# Example: npx eslint . --max-warnings 0 2>&1 | tail -40
# Example: ruff check . 2>&1 | tail -30
4. Auto-fix safe issues
# Example: npx biome check --write . 2>&1 | tail -20
# Example: black . && ruff check --fix . 2>&1 | tail -20
5. Review remaining issues
For issues that can't be auto-fixed:
- Understand the rule being violated
- Fix the root cause (not by disabling the rule)
- Only disable a rule if you understand exactly why it's a false positive
6. Re-run to confirm clean
# Run the same check commands again — must exit 0
7. Report
Lint: PASS — 0 errors, 0 warnings
Format: PASS
or
Lint: FAIL — 3 errors, 5 warnings
- error: ... (fixed)
- warning: ... (fixed)
Remaining: 0 (all resolved)
Rules
- NEVER suppress a lint rule without a written justification in a comment
- NEVER "fix" lint by converting errors to warnings
- Pre-existing lint issues: document them, do NOT fix unrelated issues
- Only fix lint issues introduced by the current change (unless asked to do a lint pass)
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.
- 1mo ago First seen · 62 lines · 30 tokens per session scan A 3d9fa2ce2491
lint is a skill published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 445 once invoked, about $0.0001 per session on Opus 5.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
implement
TRIGGER when: user asks to implement, fix, build, or work on something — whether from a docs/feat/wip plan OR a standalone task (bug fix, GitHub issue, one-off change). Examples: "work on task 1", "fix this bug", "implement feature X from the issue". Provides structured execution with profile detection, dependency…
document
After implementing a new feature or fixing a bug, make sure to document the changes. Use when writing documentation, after finishing the implementation phase for a feature or a bug-fix.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…