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 MithunWijayasiri/dotclaude --skill compact-markdowngit clone --depth 1 https://github.com/MithunWijayasiri/dotclaudeWrote 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/mithunwijayasiri/dotclaude/compact-markdown)<a href="https://agentmods.dev/skills/mithunwijayasiri/dotclaude/compact-markdown"><img src="https://agentmods.dev/badge/skills/mithunwijayasiri/dotclaude/compact-markdown/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/mithunwijayasiri/dotclaude/compact-markdown"><img src="https://agentmods.dev/badge/skills/mithunwijayasiri/dotclaude/compact-markdown.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.00085 | $0.00819 |
| Opus 5 | $0.00043 | $0.00409 |
| Sonnet 5 | $0.00017 | $0.00164 |
| Haiku 4.5 | $0.00009 | $0.00082 |
Grade A, and why
compact-markdown 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 9d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compact Markdown
Markdown docs here exist for AI agents, not human reading pleasure. Write content only. No filler, no scaffolding.
Scope
- Apply to any
.mdbeing created or edited — exceptREADME.md(skip this skill entirely for README.md). - Apply only to content you write or edit. Do not rewrite existing surrounding prose you weren't asked to touch.
- Human-facing prose in
.md(a doc written for people, not agents) → usehumanizeinstead. - Compress wording; keep markdown valid and navigable.
- Authoring a
SKILL.md? Readreferences/skill-authoring.mdfor skill-specific rules (frontmatter, triggering, what not to compact).
Core rule
Telegraphic. Drop articles, filler verbs, and pronouns where meaning survives.
- "You should run the command before testing" → "Run command before testing."
- "This function is responsible for parsing the config" → "Parses config."
- "In order to do X, you need to do Y" → "X requires Y."
- Imperative fragments are fine: "Fail → check trace." "No output → test passed."
Judgment overrides compression. Never compress if it loses important info. When in doubt, keep the words.
Strip
- Emojis, Badges.
- Filler headers — empty
## Overview/## Introductionwhose body just restates the title. Collapse into actual content or open straight with facts. - Congratulatory / motivational lines — "Great!", "Congrats!", "That's it!", "Happy coding!", "Now you're ready to...".
- Hedging and throat-clearing — "It's worth noting that", "Basically", "Simply", "Of course", "As you can see".
- Restating the prompt or the section title in the first sentence.
- Summary / Conclusion sections that only restate the doc. Keep summaries that capture decisions, risks, or takeaways.
- Table of contents for docs short enough to scan.
- Bold on every other phrase — everything emphasized = nothing emphasized.
- Horizontal rules (
---) between every section.
Keep
- Code blocks, inline code, CLI commands — verbatim, never paraphrased.
- Examples and sample snippets — they carry the most signal per token. Drop only a duplicate/low-value example, never a useful one.
- Tables — keep structured, do not flatten into prose.
- Heading hierarchy — keep for navigation. Just cut filler headers.
- Any concrete detail: paths, flags, names, values, edge cases, gotchas.
What ships with it
1 file 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.
- 9d ago First seen · 90 lines · 85 tokens per session scan A 47d5f5debea1
compact-markdown is a skill published in the GitHub repository MithunWijayasiri/dotclaude (2 stars, last pushed 4d ago), licensed MIT. It adds 85 tokens to every session and 819 once invoked, about $0.0004 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…