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 legendtkl/agents-md-polish --skill templatesgit clone --depth 1 https://github.com/legendtkl/agents-md-polishWrote 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/legendtkl/agents-md-polish/templates)<a href="https://agentmods.dev/skills/legendtkl/agents-md-polish/templates"><img src="https://agentmods.dev/badge/skills/legendtkl/agents-md-polish/templates/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/legendtkl/agents-md-polish/templates"><img src="https://agentmods.dev/badge/skills/legendtkl/agents-md-polish/templates.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.00113 | $0.01045 |
| Opus 5 | $0.00056 | $0.00522 |
| Sonnet 5 | $0.00023 | $0.00209 |
| Haiku 4.5 | $0.00011 | $0.00104 |
Grade A, and why
agents-md-polish 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents MD Polish
A short, repeatable workflow for keeping AGENTS.md and CLAUDE.md files short, project-specific, and executable. Anthropic recommends keeping CLAUDE.md under 200 lines; longer files "consume more context and reduce adherence." Bloated files cause agents to ignore your actual rules.
When invoked, run this workflow
1. Discover
Find guidance files in the current project:
AGENTS.md, CLAUDE.md
Check the repo root first, then any nested AGENTS.md files in subdirectories
(monorepos use one per package, with the closest file taking precedence).
2. Audit
Use references/audit-checklist.md to score each file. The deterministic
checks (line count, byte size, broken file references) live in
scripts/audit_agents_md.mjs — run it first:
node scripts/audit_agents_md.mjs <file>
The script exits non-zero on broken file references or missing files. Read
its JSON output (when invoked with --json) to drive follow-up actions.
3. Diagnose
For each issue, look up the matching pattern in references/polish-patterns.md
and explain the why in one sentence. Don't dump the whole pattern — just the
1-line summary so the user understands the recommendation.
4. Propose
Group the proposed changes by severity (error → warn → info). For each, show a unified diff using the Edit tool's preview format. Don't apply yet.
5. AWS test (sanity gate)
Before applying, ask of every line you would keep:
"If I remove this line, will an agent make a mistake?"
If the answer is no, propose deletion instead of modification. Bias toward shorter files.
6. Apply
Apply changes the user accepted. For long extracted content (architecture
notes, API specs, full command lists), write to docs/<topic>.md or
AGENTS-references/<topic>.md and reference from AGENTS.md by relative
path with a file:line pointer where possible.
7. Bridge-ify (if applicable)
If both AGENTS.md and CLAUDE.md exist and overlap by more than 50%, propose collapsing CLAUDE.md to a single-line bridge:
What ships with it
8 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.
- 8d ago First seen · 118 lines · 113 tokens per session scan A 3532452b50de
agents-md-polish is a skill published in the GitHub repository legendtkl/agents-md-polish (4 stars, last pushed 3mo ago), licensed MIT. It adds 113 tokens to every session and 1,045 once invoked, about $0.0006 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-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…