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 commands/bengous/claude-code-plugins/lint-auditgit clone --depth 1 https://github.com/bengous/claude-code-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.00020 | $0.01914 |
| Opus 5 | $0.00010 | $0.00957 |
| Sonnet 5 | $0.00004 | $0.00383 |
| Haiku 4.5 | $0.00002 | $0.00191 |
Grade A, and why
lint-audit 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint Rule Audit
Rule: $ARGUMENTS
Your Task
Execute a systematic lint rule audit following these phases. Take action at each phase—run commands, spawn subagents, analyze code—rather than only suggesting. Research best practices, analyze violations in the codebase, and provide actionable recommendations.
Phase 1: Discovery
Run the lint command to find all violations:
# Try common lint scripts - adapt to project
bun run lint:only $ARGUMENTS 2>/dev/null || \
bunx biome lint --only=nursery/$ARGUMENTS . 2>/dev/null || \
bunx biome lint --only=style/$ARGUMENTS . 2>/dev/null || \
bunx biome lint --only=suspicious/$ARGUMENTS .
Capture and report:
- Total violation count (errors, warnings, infos)
- Number of files affected
- Primary locations (which directories/modules)
When zero violations are found, report:
No violations found for
$ARGUMENTSin this codebase. The rule is either not enabled or the code already complies.
Then proceed directly to the Decision phase (Phase 6) with "Do nothing" as the recommended option.
Phase 2: Research
Primary Source: Biome CLI (fast, offline)
bunx biome explain $ARGUMENTS
This provides:
- Summary (name, fix availability, severity, version, category)
- Domains (framework dependencies like react@>=16.0.0)
- Full description
- Invalid examples (what gets flagged)
- Valid examples (correct patterns)
Secondary Sources (parallel subagents)
Spawn these when:
- Rule is in
nursery(experimental/controversial) - User asks for "best practices" or "modern approach"
- Biome explanation lacks context on WHY the rule exists
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.
- 2d ago First seen · 263 lines · 20 tokens per session scan A 4948117aac9a
lint-audit is a command published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 1,914 once invoked, about $0.0001 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 commands, from other repositories
pr-address
Address PR review comments on current branch.
plan-save
Save the current session's plan to GitHub as an issue.
enforce_standards
CRITICAL: Before running the code standards enforcer, we must prepare the stack properly and abort if there are merge conflicts.
OPSX: Sync
Sync delta specs from a change to main specs.
context
项目上下文管理：初始化 .context 目录、记录决策日志、压缩归档、查看历史.
OPSX: Verify
Verify implementation matches change artifacts before archiving.