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 igloude/ds-skills --skill dsgit clone --depth 1 https://github.com/igloude/ds-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/igloude/ds-skills/ds)<a href="https://agentmods.dev/skills/igloude/ds-skills/ds"><img src="https://agentmods.dev/badge/skills/igloude/ds-skills/ds.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.00027 | $0.00583 |
| Opus 5 | $0.00014 | $0.00292 |
| Sonnet 5 | $0.00005 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
ds 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 7d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ds — the router
Three sibling skills police design-system conformance. All are report-only — they write verdicts, maps, and plans, never code. This skill only routes; when the user's intent matches a row below, tell them the command (or invoke the named skill if they ask you to proceed).
/ds-doctor → audits the DS itself, writes ds/MANIFEST.md + ds/tokens.json
└→ everything below reads it
/ds-plan → classifies a feature's UI against the DS before it is built
├→ Covered / Composable → exact props, to the generators
└→ Extension / Net-new → DS work items → the DS backlog
generators → N branches of AI work
/ds-drift → reviews finished code for DS conformance
├→ reviews: verdicts + specs → back to the generators
└→ plans: self-contained specs → cheap executor, or --issues
Reach for
/ds-drift— the work exists and needs judging: gate a branch or PR, batch-review parallel agent branches, sweep a repo for token/adoption/a11y drift, audit a DS version upgrade, orreconcilethe backlog./ds-plan— the work doesn't exist yet: a ticket, spec, or design needs classifying against the DS, sequencing into DS-repo vs app-repo waves, or a quick "do we have something for this?" (element)./ds-doctor— the design system itself is the subject: is it enforceable, where are the doc/token/policy gaps, and generate or refresh the conformance manifest (runmanifestafter every DS release).
The loop
- In the DS repo:
/ds-doctor, fix blockers,/ds-doctor manifest, publishds/with the package. - Before a feature:
/ds-plan <ticket|design>in the app repo; ship Wave 0 DS work, hand the map to the building agent. - After generation:
/ds-drifton the branch (orbatchacross parallel branches); feed the review back to the generator. - Periodically:
/ds-drift sweepfor the baseline,coveragefor the trendline,reconcileto keep the record honest.
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.
- 7d ago First seen · 42 lines · 27 tokens per session scan A 229f2229f3f0
ds is a skill published in the GitHub repository igloude/ds-skills (8 stars, last pushed 18d ago), licensed MIT. It adds 27 tokens to every session and 583 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
system-pitch
Write a design system investment pitch with a business case and ROI framing. Trigger when someone says: pitch the design system, make the case for the system, sell this to leadership, justify the investment, business case for design systems, why should we invest in a design system, or anything about building an…
ai-component-description
Generate AI-optimised text descriptions for components, formatted for Figma's MCP server and LLM consumption. This produces prose descriptions in a six-section format (purpose, props, anti-patterns, composition, accessibility, examples), NOT JSON schemas or structured data files. Trigger when someone says: write…
stakeholder-brief
Write a one-page stakeholder brief translating design system health or status into business language. Trigger when someone says: stakeholder update, exec brief, leadership summary, status report for leadership, system status for non-designers, write a brief for the business, or anything about communicating design…
token-audit
Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…
accessibility-per-component
Run an accessibility audit on a specific design system component. Trigger when someone says: accessibility check, a11y audit, WCAG compliance, is this accessible, check accessibility, does this meet WCAG, screen reader support, keyboard navigation check, or anything about auditing the accessibility of a specific…
context-engine-builder
Generate a context engine — seven structured blueprint files (UX, UI, content, accessibility, ethical, technical, business intelligence) that encode everything an AI agent needs to work with a design system. This produces YAML infrastructure in .ai/context-engine/, NOT a health score or quality assessment. Trigger…