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 William-Yeh/agent-skill-linter --skill skillgit clone --depth 1 https://github.com/William-Yeh/agent-skill-linterWrote 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/william-yeh/agent-skill-linter/skill)<a href="https://agentmods.dev/skills/william-yeh/agent-skill-linter/skill"><img src="https://agentmods.dev/badge/skills/william-yeh/agent-skill-linter/skill.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.1 | $0.00019 | $0.02308 |
| Opus 5 | $0.00010 | $0.01154 |
| Sonnet 5 | $0.00004 | $0.00462 |
| Haiku 4.5 | $0.00002 | $0.00231 |
Grade A, and why
agent-skill-linter 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 today.
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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Skill Linter
Checks agent skills for spec compliance and publishing readiness.
Expected Layouts
Two layouts are supported, auto-detected by presence of .claude-plugin/plugin.json at the target:
- Single skill — lint target is the
skill/subdir (or repo root for legacy repos). - Plugin — lint target is the plugin root; manifest + each
skills/<name>/checked.
See
references/layouts.mdfor layout diagrams, file-by-file conventions, and per-mode detection rules.
Triage Workflow
Target: the skill directory to lint — current directory (.) or a path provided by the user.
Step 1 — Get the full picture
./scripts/skill-lint.py check <target>
Review the output for errors and warnings; confirm the full picture before proceeding to Step 2.
Step 2 — Fix Errors first
Rule 1 (SKILL.md spec compliance) blocks publishing. Fix before anything else.
Step 3 — Auto-fix Warnings
./scripts/skill-lint.py check <target> --fix
For fixable rules without CLI, use the templates in references/fix-templates.md.
Confirm no auto-fixable warnings remain before continuing to Step 4.
Step 4 — Resolve remaining Warnings manually
CSO description prefix (Rule 11), Python invocations (Rule 13), README-tier sections in SKILL.md (Rule 19) — see the rule table below.
Confirm all remaining warnings are resolved (or explicitly accepted) before proceeding to Step 5.
Step 5 — Semantic review: CSO signal
Rule 11 catches structural patterns but not meaning. Read the description and name frontmatter and ask: do they function purely as routing signals?
See
references/semantic-rules.md— Rules 12 and 18 for examples.
Flag the description if it:
- Enumerates what the skill checks, handles, or supports
- Reads as a feature summary or workflow overview
- Contains elaboration labels (
Triggers on:,Use cases:,Checks:) or multiple sentences - Could be trimmed to one clause without losing routing precision
What ships with it
10 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.
- references/fix-templates.md 3.1 KB
- references/layouts.md 1.9 KB
- references/semantic-rules.md 14 KB
- scripts/.gitignore 19 B
- scripts/fixers.py 15 KB runs code
- scripts/linter.py 3.8 KB runs code
- scripts/models.py 357 B runs code
- scripts/prose.py 7.4 KB runs code
- scripts/rules.py 38 KB runs code
- scripts/skill-lint.py 3.3 KB runs code
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.
- today Changed · +13 lines 11ab8367428e
- 7d ago First seen · 179 lines · 19 tokens per session scan A 32f6994b747e
agent-skill-linter is a skill published in the GitHub repository William-Yeh/agent-skill-linter (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 2,308 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…