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 agentmods add skills/ericboehs/claude-plugins/setup-lintnpx skills add ericboehs/claude-plugins --skill setup-lintgit clone --depth 1 https://github.com/ericboehs/claude-pluginsWhat 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 | $0.00039 | $0.01949 |
| Opus 5 | $0.00019 | $0.00975 |
| Sonnet 5 | $0.00008 | $0.00390 |
| Haiku 4.5 | $0.00004 | $0.00195 |
Grade A, and why
setup-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 yesterday.
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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Lint
Interactive setup wizard for the code-lint plugin. Detects project languages and linters, asks what to enable, writes per-project config.
Step 1: Detect Project
Run the detection script to discover languages, linter configs, and available binaries:
bash "${CLAUDE_PLUGIN_ROOT}/skills/setup-lint/scripts/detect-project.sh" "${CLAUDE_PROJECT_DIR:-$(pwd)}"
If CLAUDE_PLUGIN_ROOT is not set, find the script relative to this SKILL.md file (./scripts/detect-project.sh).
Parse the JSON output — it describes which languages are present and which linters are available/configured.
Step 2: Interview User
For each detected language, use AskUserQuestion to confirm:
- Language enablement: "I found Ruby files (Gemfile, .rubocop.yml). Enable Ruby linting?"
- Linter selection: "rubocop and reek are available. Which linters do you want to enable?"
- Autofix: "Auto-fix style issues before checking? (rubocop -A will run before rubocop lint)"
- Exclusions: "Any paths to exclude beyond defaults? (Current defaults: test/, spec/, db/schema.rb)"
Defaults to suggest
Ruby:
- Enable: rubocop, reek
- Exclude:
test/,spec/,db/schema.rb - Autofix: rubocop only
JavaScript/TypeScript:
- Enable: eslint (or biome if configured)
- Exclude:
node_modules/,dist/,build/ - Autofix: eslint --fix (or biome --write)
Python:
- Enable: ruff (preferred), flake8 as fallback
- Exclude:
.venv/,__pycache__/,migrations/ - Autofix: ruff --fix
Go:
- Enable: golangci-lint
- Exclude:
vendor/
Rust:
- Enable: clippy (whole-project only — won't run in hooks, only in /lint)
Markdown:
- Enable: markdownlint
- Exclude:
node_modules/,vendor/ - Autofix: markdownlint --fix
HTML:
- Enable: prettier (for check + format)
- Exclude:
node_modules/,dist/,build/ - Autofix: prettier --write
Shell:
- Enable: shellcheck
- Exclude:
node_modules/,vendor/
Tool linters (language-agnostic)
After the per-language interview, check for tool linters detected in the JSON output (tool_linters key).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 210 lines · 39 tokens per session scan A 8ed898282122
setup-lint is a skill published in the GitHub repository ericboehs/claude-plugins (2 stars, last pushed 8d ago), licensed MIT. It adds 39 tokens to every session and 1,949 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…