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/elbalen/skopus/lintgit clone --depth 1 https://github.com/elbalen/skopusWrote 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/elbalen/skopus/lint)<a href="https://agentmods.dev/commands/elbalen/skopus/lint"><img src="https://agentmods.dev/badge/commands/elbalen/skopus/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.00007 | $0.00440 |
| Opus 5 | $0.00003 | $0.00220 |
| Sonnet 5 | $0.00001 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
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
/lint
Scan the wiki for integrity issues and report a health report with suggested fixes. Auto-fix safe cases on request.
No arguments.
Steps
-
Scan every
.mdfile inwiki/viaGlob: wiki/**/*.md. -
Extract all
[[wikilinks]]from every page. Track source page and link target. -
Build inbound link counts (excluding
index.md). -
Check each wikilink target resolves to an existing page.
-
Check
updated:frontmatter dates. Flag pages older than 30 days. -
Scan for repeated terms that don't have their own page yet (capitalized terms, technical terms appearing 3+ times).
-
Look for potential contradictions — same entity described differently across pages.
-
Print a health report:
📊 Wiki Health Report Totals: Pages, Links, Words, Sources ❌ Broken wikilinks (N) 🏝️ Orphan pages (N) 🕸️ Stale pages (N) 📝 Suggested new pages (N) ⚠️ Potential contradictions (N) -
Offer to auto-fix safe cases:
- Broken wikilinks → create stub pages OR remove links (user chooses)
- Missing index entries → add them automatically
-
Append lint results to
log.md. -
Git commit if any fixes were applied:
lint: fix <N> <issue type>.
Rules
- Report before fixing. Always show the full report first.
- Auto-fixes are safe only. Creating stubs and updating index entries are safe. Deleting/merging require confirmation.
- Stub pages get
type: stuband a> ⚠️ Stub: needs contentcallout. - Don't flag pages created in the last 7 days as stale.
index.mdis excluded from orphan/inbound counts.
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 · 55 lines · 7 tokens per session scan A 76b74462d344
lint is a command published in the GitHub repository elbalen/skopus (4 stars, last pushed 4mo ago), licensed MIT. It adds 7 tokens to every session and 440 once invoked, about $0.0000 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.