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/lintnpx skills add ericboehs/claude-plugins --skill 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.00036 | $0.01344 |
| Opus 5 | $0.00018 | $0.00672 |
| Sonnet 5 | $0.00007 | $0.00269 |
| Haiku 4.5 | $0.00004 | $0.00134 |
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 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint
Run configured linters across the full project. Includes whole-project-only linters (brakeman, clippy) that don't run in the PostToolUse hook.
Usage
/lint— Run all enabled linters on the full project/lint ruby— Run only Ruby linters/lint reek— Run only the reek linter/lint semgrep— Run only Semgrep (tool linter)/lint --fix— Run autofix on all files first, then lint
Arguments after /lint are parsed as:
- A language name (ruby, javascript, python, go, rust, markdown, html, shell) → filter to that language
- A linter name (rubocop, reek, eslint, ruff, etc.) → filter to that specific linter
- A tool linter name (semgrep) → filter to that tool linter
--fix→ run autofix commands before linting
Step 1: Load Config
PROJECT_DIR="${CLAUDE_PROJECT_DIR:-$(pwd)}"
PROJECT_HASH=$(echo "$PROJECT_DIR" | tr '/' '-' | sed 's/^-//')
CONFIG_FILE="$HOME/.claude/code-lint/$PROJECT_HASH/config.json"
If no config exists, tell the user to run /setup-lint first.
Read and parse the config JSON.
Step 2: Determine Scope
Parse arguments to determine what to run:
- No args → all enabled languages, all enabled linters
- Language arg → only that language's linters
- Linter arg → only that specific linter
--fix→ enable autofix mode
Step 3: Run Linters
For each enabled linter in scope:
Single-file linters
Find all matching files (using file_patterns), excluding paths that match exclude_patterns. Run the linter on all matching files at once (most linters accept multiple files or directories).
cd "$PROJECT_DIR"
# If --fix mode, run autofix first
bundle exec rubocop -A --fail-level=error .
# Then run the lint check
bundle exec rubocop .
Whole-project-only linters
Run these against the project root:
cd "$PROJECT_DIR"
bundle exec brakeman -q
cargo clippy -- -D warnings
Tool linters (e.g. Semgrep)
After running per-language linters, check the tool_linters section of the config. For each enabled tool linter:
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 · 167 lines · 36 tokens per session scan A 44ae86b13f1b
lint is a skill published in the GitHub repository ericboehs/claude-plugins (2 stars, last pushed 8d ago), licensed MIT. It adds 36 tokens to every session and 1,344 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…