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 ZachArticulateV/designer-pro-and-seo --skill design-system-persistgit clone --depth 1 https://github.com/ZachArticulateV/designer-pro-and-seoWrote 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/zacharticulatev/designer-pro-and-seo/design-system-persist)<a href="https://agentmods.dev/skills/zacharticulatev/designer-pro-and-seo/design-system-persist"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/design-system-persist/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/zacharticulatev/designer-pro-and-seo/design-system-persist"><img src="https://agentmods.dev/badge/skills/zacharticulatev/designer-pro-and-seo/design-system-persist.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.00072 | $0.00644 |
| Opus 5 | $0.00036 | $0.00322 |
| Sonnet 5 | $0.00014 | $0.00129 |
| Haiku 4.5 | $0.00007 | $0.00064 |
Grade A, and why
design-system-persist 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 12d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
design-system-persist
Family: design Status: Stable
Purpose
Save a design system into a project's design-system/ folder so it survives across
sessions and is shared across skills. Uses a Master + Overrides pattern:
design-system/MASTER.md— the global system (every page inherits it by default)design-system/pages/<page-name>.md— per-page overrides (clean deviations)
Future sessions check pages/<current-page>.md first; if present, its rules
override Master, else Master applies. A 12-page site gets one Master + small page
files instead of one bloated spec enumerating every exception inline.
Triggers
- "save the design system" / "persist this"
- "make this the master"
- "remember these design choices"
- "design system to disk"
Inputs
- A design system spec (from
design-system-gen, or pasted by the user) - Project root path
- Page name (optional — for a per-page override)
Steps
- Get the design system. Use a
design-system-genresult (JSON or ASCII) or the spec the user pasted. - Locate/create
design-system/at the project root (andpages/if saving an override). - Fill the starter template
templates/design-system-starter.md: map the palette hex + contrast, typography + weights, pattern, style, effects, anti-patterns, and the pre-delivery checklist into its slots. - Write the file:
- Master →
design-system/MASTER.md - Page override →
design-system/pages/<name>.mdwith explicit deviation + reason notes (keep deviations minimal).
- Master →
- Write/refresh
design-system/README.mdexplaining the structure to future agents. - Emit a retrieval prompt for the next session, e.g.: "I'm building [page]. Read design-system/MASTER.md; also check design-system/pages/[name].md — page rules override Master."
Outputs
design-system/MASTER.md(and/orpages/<name>.md)design-system/README.md- A paste-ready context-retrieval prompt for the next session
Dependencies
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.
- 12d ago First seen · 71 lines · 72 tokens per session scan A cf4cd6536894
design-system-persist is a skill published in the GitHub repository ZachArticulateV/designer-pro-and-seo (8 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 644 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
extract-design
Extract the full design language from any website URL. Produces 8 output files including AI-optimized markdown, visual HTML preview, Tailwind config, React theme, shadcn/ui theme, Figma variables, W3C design tokens, and CSS variables. Also runs WCAG accessibility scoring. Use when user says 'extract design', 'get…
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
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…
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…
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…