lint

lint is a skill for Claude Code from brain-bootstrap/claude-code-brain-bootstrap. It costs 30 tokens per session (445 once invoked), scanned A, original, MIT.

A procedure for running a project's formatter and linter, which check code style and common programming mistakes, and fixing issues that can be safely corrected automatically.

In plain words
What is it for?
Use it before opening a pull request to find, auto-fix, and verify formatting and lint errors using the commands defined by the project.
Why use it?
It catches style and code-quality problems before a pull request and requires remaining warnings to be reviewed rather than hidden.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it before opening a pull request to find, auto-fix, and verify formatting and lint errors using the commands defined by the project.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/brain-bootstrap/claude-code-brain-bootstrap/lint
Install

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.

Any agent
npx skills add brain-bootstrap/claude-code-brain-bootstrap --skill lint
Clone the repo
git clone --depth 1 https://github.com/brain-bootstrap/claude-code-brain-bootstrap

Made for: Claude Code.

Wrote 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.

agentmods badge for lint

README.md
[![agentmods](https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/lint/github.svg)](https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/lint)
Your own site
<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.

agentmods 80×15 button for lint

Your own site · 80×15
<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>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 445 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash 3d9fa2ce2491, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.claude/skills/lint/SKILL.md · 62 lines

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)
Changes

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.

  1. 1mo ago First seen · 62 lines · 30 tokens per session scan A 3d9fa2ce2491

Subscribe to this mod's changes

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.

Related

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…

serpro69/claude-toolbox · 81 tokens

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.

serpro69/claude-toolbox · 38 tokens

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…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

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.

open-metadata/OpenMetadata · 37 tokens

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.

emdash-cms/emdash · 48 tokens

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…

zebbern/claude-code-guide · 71 tokens