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 skills add zernie/vigiles --skill linter-docsgit clone --depth 1 https://github.com/zernie/vigilesWrote 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/skills/zernie/vigiles/linter-docs)<a href="https://agentmods.dev/skills/zernie/vigiles/linter-docs"><img src="https://agentmods.dev/badge/skills/zernie/vigiles/linter-docs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zernie/vigiles/linter-docs"><img src="https://agentmods.dev/badge/skills/zernie/vigiles/linter-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.1 | $0.00125 | $0.00532 |
| Opus 5.5 | $0.00050 | $0.00213 |
| Sonnet 5.5 | $0.00025 | $0.00106 |
| Haiku 4.5 | $0.00013 | $0.00053 |
Grade A, and why
linter-docs 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 1mo 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
Reference material for the linters vigiles cross-references. Open the file for
the linter you're working with when you need exact rule names, AST selectors,
or config details to author an enforce() rule (or diagnose why one is reported
missing or disabled).
| Linter | Reference |
|---|---|
| ESLint | eslint.md — plugin table, AST selectors, type-aware rules, auto-fix |
| Ruff | ruff.md — 800+ reimplemented rules, selection, auto-fix, pyproject config |
| Pylint | pylint.md — plugin table, astroid AST, type inference, custom checkers |
| RuboCop | rubocop.md — gem table, node pattern DSL, auto-correct, custom cops |
| Stylelint | stylelint.md — plugin table, PostCSS AST, custom rules, SCSS |
| Clippy | clippy.md — Rust lint groups and configuration |
JVM/Go linters (detekt, ktlint, Checkstyle, golangci-lint) and Cedar are
cross-referenced by enforce() but have no deep-dive file here yet — their
capabilities, config surfaces, and known limits (e.g. ktlint is format-only,
Checkstyle enabled-state is whitelist-only) are documented in
docs/linter-support.md.
These are read by the strengthen and edit-spec skills when matching a
guidance rule to a real linter rule. This skill is user-invoked (a reference,
not an action), so it never fires on its own — open the relevant file directly.
What ships with it
6 files 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.
- 1mo ago First seen · 30 lines · 125 tokens per session scan A 846ce8b994cc
linter-docs is a skill published in the GitHub repository zernie/vigiles (15 stars, last pushed 11d ago), licensed MIT. It adds 125 tokens to every session and 532 once invoked, about $0.0005 per session on Opus 5.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-30.
Other skills, from other repositories
five-whys
Finds the root cause of a bug, failure or recurring problem by asking "why" until the answer is a cause you can fix. Use when the user asks why something keeps happening, or wants the root cause rather than a quick fix.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524): sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
sandbox-unblock
Diagnostic protocol to run before reporting a sandbox blocker or asking for a configuration change. Eleven checks that eliminate false positives, then a report template the person holding the settings can act on. On one measured day, six of eight reported blockers turned out to be false, all from the same handful of…
investigate
Systematic root-cause debugging: find the cause before writing any fix.
qa
Systematic QA testing of a web application: diff-aware, tiered, with fix-and-verify loop.
optimize
Analyze and suggest performance improvements for code, queries, or systems.