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/lintgit 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)<a href="https://agentmods.dev/commands/ruslan-korneev/claude-plugins/lint"><img src="https://agentmods.dev/badge/commands/ruslan-korneev/claude-plugins/lint.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.00016 | $0.00451 |
| Opus 5 | $0.00008 | $0.00226 |
| Sonnet 5 | $0.00003 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
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 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.
What it actually says
Command /lint:check
Run Python code analysis using ruff.
Instructions
-
Run
ruff checkfor the specified path (or current directory if no path is specified):ruff check {{ path | default: "." }} --output-format=grouped -
Analyze the result and group errors by category:
- Style errors (E, W): formatting, whitespace, line length
- Potential bugs (F): unused imports, variables, syntax errors
- Code complexity (C): cognitive complexity, nesting
- Security (S): potential vulnerabilities
- Library-specific (B, UP, etc.)
-
For each error group:
- Show the error count
- Provide examples with line numbers
- Suggest a fix strategy
-
IMPORTANT: NEVER suggest
# noqaas a solution!- Every ruff error has a proper solution
- If the user asks about a specific error, use
/lint:explain
Output Format
## Ruff Check Results
### Errors found: X
#### Style errors (E/W): N
- E501: Lines too long (5 files)
- W291: Trailing whitespace (2 files)
#### Potential bugs (F): N
- F401: Unused imports (3 files)
- F841: Unused variables (1 file)
### Auto-fixable
Run `ruff check --fix` to automatically fix X errors.
### Require manual fix
- E501 in src/services/user.py:45 - split into multiple lines
- ...
Additional Flags
If the user wants more detailed output:
--statistics- show statistics by rules--show-fixes- show which fixes can be applied automatically
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 · 69 lines · 16 tokens per session scan A a9f0ed8538d7
lint is a command published in the GitHub repository ruslan-korneev/claude-plugins (4 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 451 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 hooks have ever fired and which copy of the plugin ran them, the usage ledger, whether the audit trail still…
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…