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/ruslan-korneev/claude-plugins/lint-explaingit clone --depth 1 https://github.com/ruslan-korneev/claude-pluginsWrote 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/commands/ruslan-korneev/claude-plugins/lint-explain)<a href="https://agentmods.dev/commands/ruslan-korneev/claude-plugins/lint-explain"><img src="https://agentmods.dev/badge/commands/ruslan-korneev/claude-plugins/lint-explain.svg" alt="Measured on agentmods" 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 | $0.00023 | $0.01309 |
| Opus 5 | $0.00012 | $0.00655 |
| Sonnet 5 | $0.00005 | $0.00262 |
| Haiku 4.5 | $0.00002 | $0.00131 |
Grade A, and why
lint:explain 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 4d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command /lint:explain
Explain a ruff error and show the PROPER solution. NEVER suggest # noqa!
Instructions
Step 1: Determine Input Type
The user may specify:
- Rule code:
E501,F401,B008 - Path with line number:
src/main.py:15 - Rule code + path:
E501 src/main.py:15
Step 2: Get Error Information
ruff rule {{ error_code }}
If a file is specified, read the context:
ruff check {{ file_path }} --output-format=json
Step 3: Explain the Error
For each error explain:
- What it means - in plain language
- Why it's bad - real consequences
- How to fix - concrete example
Step 4: Show Solution
CRITICAL: Always show the proper solution, not # noqa!
Solution Database for Popular Errors
E501: Line too long
# Bad
result = some_function(very_long_argument_name, another_long_argument, yet_another_one, and_more)
# Good - use parentheses for line breaks
result = some_function(
very_long_argument_name,
another_long_argument,
yet_another_one,
and_more,
)
# For strings - use concatenation or textwrap
message = (
"This is a very long message that would exceed "
"the line length limit if written on one line"
)
F401: Unused import
# Bad
from typing import List, Dict, Optional # Dict is not used
# Good - remove unused import
from typing import List, Optional
# If import is needed for re-export:
from .models import User as User # explicit re-export via `as`
# or add to __all__
__all__ = ["User"]
F841: Local variable assigned but never used
# Bad
def process():
result = expensive_calculation() # result is not used
return True
# Good - use underscore to explicitly ignore
def process():
_ = expensive_calculation() # explicitly show result is not needed
return True
# Or remove the assignment if result is not needed
def process():
expensive_calculation()
return True
B008: Do not perform function calls in argument defaults
# Bad
def process(items: list = []): # mutable default!
items.append(1)
return items
# Good - use None and check
def process(items: list | None = None):
if items is None:
items = []
items.append(1)
return items
# For FastAPI Depends - this is normal, add to ignore:
# [tool.ruff.lint.per-file-ignores]
# "src/*/routers.py" = ["B008"]
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.
- 4d ago First seen · 235 lines · 23 tokens per session scan A a64aab83a830
lint:explain is a command published in the GitHub repository ruslan-korneev/claude-plugins (4 stars, last pushed 6mo ago), licensed MIT. It adds 23 tokens to every session and 1,309 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
sync
Sync the audit manifest with Azure DevOps work items — set the connector up for the first time (connect: verify the transport, report which auth path is in effect, prove access read-only, detect the board's process), push manifest bugs/tasks/phases to ADO (board states, sprint stamp, Remaining Work, comments), pull…
init
Multi-agent codebase audit that GENERATES the audit manifest (phases/tasks) at manifestPath. Interviews you for scope/goals, fans out parallel read-only explorers, synthesizes findings, then presents the proposed phases for approval BEFORE writing — approve to materialize, or park them as proposals for later…
task
Add a tracked task to the audit manifest — every answer is a flag, and the dialogue only covers what the caller did not pass — move one between phases, or cancel work that will not be done. add allocates the id, initializes all orchestrator fields, updates fileIndex, and revalidates; move renumbers a task into another…
panel
Audit pipeline: open / stop / check a local control-panel UI to visually manage .claude/audit.config.json and the manifest's composition levers (reviewSkill, per-task skills/models, buildCommands) — with live validation and discovery of the skills & agents available in this repo + globally. Ephemeral, on-demand; a…
doctor
Audit pipeline: diagnose the setup before it bites — interpreter the hooks will use, git root, config, manifest + shard integrity, which plan-gate tier is active, submodule conflicts, build runners, whether the skills the plan names would resolve from a clone or only here, whether hooks have ever fired and which copy…
layout
Audit pipeline: choose how the manifest is stored — sharded (an index plus one file per phase: fewer tokens per phase run, parallel-safe across worktrees) or single-file (one file, one diff, no index). A layout CHOICE, not a version upgrade: both shapes are current, neither goes out of date, and this command moves in…