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.
git clone --depth 1 https://github.com/doneyli/claude-code-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/doneyli/claude-code-plugins/lint)<a href="https://agentmods.dev/commands/doneyli/claude-code-plugins/lint"><img src="https://agentmods.dev/badge/commands/doneyli/claude-code-plugins/lint/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/commands/doneyli/claude-code-plugins/lint"><img src="https://agentmods.dev/badge/commands/doneyli/claude-code-plugins/lint.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00027 | $0.00514 |
| Opus 5.5 | $0.00011 | $0.00206 |
| Sonnet 5.5 | $0.00005 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00051 |
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 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
Lint the wiki in the current directory. Output a report grouped by check type.
For each .md file under wiki/ (skip wiki/log.md):
-
Frontmatter validation
- YAML frontmatter exists between
---markers - Required fields:
title,type,created,last_updated confidence∈ {high, medium, low} if presentttlmatches^\d+d$or is nullcreated/last_updatedmatch YYYY-MM-DD
- YAML frontmatter exists between
-
Link integrity
- Every
[[wikilink]]resolves to an existing wiki page - Report broken links with file:line
- Every
-
Orphans
- Count inbound
[[references]]to each page - Pages with 0 inbound (except
wiki/index.md) are orphans - Exception: synthesis pages linked from
wiki/index.md
- Count inbound
-
Backlinks section audit
- Every page has a
## Backlinksheading (warn if missing)
- Every page has a
-
Staleness
last_updated + ttl < today→ stale- Skip pages with
ttl: null
-
Source attribution
- Pages with type ∈ {entity, concept, theme, capability, narrative, client, pattern} have non-empty
sources: - Synthesis and comparison pages may have empty
sources:
- Pages with type ∈ {entity, concept, theme, capability, narrative, client, pattern} have non-empty
Output format:
=== Frontmatter ===
✗ wiki/entities/foo.md: missing required field 'type'
=== Links ===
✗ wiki/concepts/bar.md:15: broken link [[nonexistent]]
=== Orphans ===
⚠ wiki/themes/lonely.md: 0 inbound links
=== Staleness ===
⚠ wiki/entities/old.md: stale (last_updated 2025-01-01, ttl 90d)
=== Attribution ===
✗ wiki/entities/foo.md: type 'entity' requires non-empty sources:
=== Summary ===
N errors, M warnings (K pages checked)
If there are errors, suggest specific fixes — but do NOT auto-fix unless the user asks. Just report.
Do not invent issues. If the wiki is clean, print Healthy — 0 errors, 0 warnings.
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 · 61 lines · 27 tokens per session scan A 217bdd682b14
lint is a command published in the GitHub repository doneyli/claude-code-plugins (4 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 514 once invoked, about $0.0001 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-31.
Other commands, from other repositories
wikimate-lint
A read-only health check for an Obsidian vault, a folder of linked Markdown notes. It scans for duplicate notes, broken links, orphaned notes, frontmatter problems, and incomplete indexes.
lint
Run comprehensive wiki health check — orphans, broken links, contradictions, stale pages, index sync, MOC coverage, v2/v4/v5 frontmatter coverage, Core Context freshness, and cross-vault link integrity (mainVaultRelated/mainVaultCmds).
debug-formula
A command for checking and debugging formulas in a selected area.
wiki-lint
Run a health check on the LLM Wiki vault — mechanical checks (orphans, broken links, stale pages, missing frontmatter, log gap, duplicates) plus semantic checks (contradictions, cross-reference gaps, concepts missing their own page). Outputs a markdown report with suggested actions. Usage /wiki-lint [--stale-days N]…
validate
Bulk frontmatter validation across your Obsidian vault.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…