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 HashLips/agent-skills --skill md-design-systemgit clone --depth 1 https://github.com/HashLips/agent-skillsWrote 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/hashlips/agent-skills/md-design-system)<a href="https://agentmods.dev/skills/hashlips/agent-skills/md-design-system"><img src="https://agentmods.dev/badge/skills/hashlips/agent-skills/md-design-system.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.00044 | $0.00489 |
| Opus 5 | $0.00022 | $0.00244 |
| Sonnet 5 | $0.00009 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
md-design-system 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.
What it actually says
MD Design System
Use this as a lightweight formatter contract.
Core Rules
- Format only — never change facts, decisions, constraints, or values.
- Template first — if another skill defines required sections/fields, keep them.
- One H1 + no heading skips —
#then##then###then####. - Lists over prose — prefer bullets and steps for scanability.
- Named items over tables — use
- **name** — valuefor fields/interfaces. - Canonical syntax —
-bullets,1.ordered lists, fenced code,[label](url). - Lean output — remove decorative noise and repetition.
- Canonical filenames — enforce kebab-case,
-agent.mdfor agents, andSKILL.mdas skill entry file.
Workflow
- Choose scope:
- Single-file edit -> follow lightweight flow.
- Package refactor -> use package mode from references/context-budget.md.
- Pick document profile from references/canonical-profiles.md.
- Keep template-required sections and field placement intact.
- Normalize headings, lists, variables/interfaces, and code formatting.
- Run references/normalization-checklist.md.
Reference Index
- Profiles (section order): references/canonical-profiles.md
- Molecules (section shapes): references/molecules.md
- Syntax rules: references/canonical-syntax.md
- QA and fact-preservation checks: references/normalization-checklist.md
- Context policy: references/context-budget.md
When To Use This Skill
- Formatting/refactoring Markdown for consistent structure.
- Applying style contracts without changing meaning.
- Enforcing predictable, lean outputs across skills and agents.
What ships with it
5 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 · 44 lines · 44 tokens per session scan A 21d28ab5d5d0
md-design-system is a skill published in the GitHub repository HashLips/agent-skills (24 stars, last pushed 13d ago), licensed MIT. It adds 44 tokens to every session and 489 once invoked, about $0.0002 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-30.
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…