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 mrstev3n/balise-skills --skill balise-design-systemgit clone --depth 1 https://github.com/mrstev3n/balise-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/mrstev3n/balise-skills/balise-design-system)<a href="https://agentmods.dev/skills/mrstev3n/balise-skills/balise-design-system"><img src="https://agentmods.dev/badge/skills/mrstev3n/balise-skills/balise-design-system/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/mrstev3n/balise-skills/balise-design-system"><img src="https://agentmods.dev/badge/skills/mrstev3n/balise-skills/balise-design-system.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00205 | $0.02641 |
| Opus 5 | $0.00102 | $0.01321 |
| Sonnet 5 | $0.00041 | $0.00528 |
| Haiku 4.5 | $0.00020 | $0.00264 |
Grade A, and why
balise-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 13d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design System
Concevoir le système comme un produit partagé : décisions, composants, documentation, distribution et gouvernance. Ne jamais réduire la réponse à une palette, un fichier de variables ou une bibliothèque isolée.
Choisir le workflow
Qualifier la demande avant d’agir :
| Demande | Point de départ | Sortie principale |
|---|---|---|
| Définir une approche | contexte, finalité, consommateurs | brief, options, architecture, pilote |
| Auditer l’existant | code, design, docs, usages | inventaire, divergences, dette, priorités |
| Créer ou migrer des tokens | produits, modes, plateformes | taxonomie, source, mappings, pipeline |
| Construire les fondations | usages et contraintes réels | rampes, rôles, échelles, validations |
| Structurer Figma et relier au code | styles, variables, collections, composants | mapping, autorités, preuves de synchronisation |
| Consolider un SaaS | navigation, données, formulaires, tenants | fondations, patterns, états, densité, thèmes |
| Adapter Tailwind ou une base UI | version, conventions, dette, API existante | stratégie extend/override/replace, pont sémantique |
| Spécifier un composant/pattern | problème, contexte, états | contrat, API, comportement, preuves |
| Guider la consommation | rôles et points de friction | golden path, extension, contribution, upgrade |
| Organiser la gouvernance | équipe, capacité, risques | ownership, maturité, release, métriques |
Lire seulement les références nécessaires :
- Stratégie, périmètre et modèle d’organisation : references/strategy-and-scope.md
- Audits, inventaires et sélection du pilote : references/audits-and-pilots.md
- Architecture DTCG, couches, alias, thèmes et modes : references/token-architecture.md
- Nommage et autorités design/code/docs : references/naming-and-source-authority.md
- Couleur, typographie, espace et autres fondations : references/color-and-typography.md
- Primitives UI, composants, patterns et états : references/components-and-patterns.md
- Parcours consommateur, onboarding et documentation : references/consumption-and-learning.md
- Gouvernance, maturité, contribution et mesure : references/governance-and-maturity.md
- Transformations, packages, tests, releases et migrations : references/implementation-pipelines.md
- Style Dictionary, cycle de compilation et critères d’adoption : references/style-dictionary.md
- Variables, styles, bibliothèques et passage Figma → code : references/figma-to-code.md
- Fondations et patterns structurels pour produits SaaS : references/saas-structures.md
- Adoption de Tailwind, shadcn et autres bases UI : references/framework-adoption.md
- Fiches, matrices et contrats de livraison : references/deliverable-templates.md
What ships with it
16 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.
- references/audits-and-pilots.md 12 KB
- references/color-and-typography.md 5.1 KB
- references/components-and-patterns.md 4.1 KB
- references/consumption-and-learning.md 3.0 KB
- references/deliverable-templates.md 4.3 KB
- references/figma-to-code.md 6.9 KB
- references/framework-adoption.md 7.4 KB
- references/governance-and-maturity.md 13 KB
- references/implementation-pipelines.md 4.5 KB
- references/naming-and-source-authority.md 3.0 KB
- references/saas-structures.md 6.8 KB
- references/strategy-and-scope.md 12 KB
- references/style-dictionary.md 9.2 KB
- references/token-architecture.md 6.4 KB
- scripts/audit_token_usage.py 6.0 KB runs code
- scripts/validate_dtcg.py 11 KB runs code
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.
- 13d ago First seen · 221 lines · 205 tokens per session scan A 31edc44b9c8e
balise-design-system is a skill published in the GitHub repository mrstev3n/balise-skills (11 stars, last pushed 24d ago), licensed Apache-2.0. It adds 205 tokens to every session and 2,641 once invoked, about $0.0010 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
ijfw-ui-spec
Use when the user says: 'ui spec', 'design contract', 'ui audit setup', 'lock the design', 'visual contract', 'ui review setup', or '/ijfw-ui-spec'. Produces UI-SPEC.md as the visual design contract before any frontend or visual-artifact build, and dispatches ijfw-ui-auditor as the final 6-pillar gate.
ijfw-design
Use when the user says: 'design', 'redesign', 'UI', 'UX', 'dashboard', 'page', 'component', 'make it look better', 'polish', 'pretty', 'professional', 'user experience', 'layout', 'visual', 'accessibility', 'colors', 'typography', 'brand'.
Add Claude design-system and accessibility workflows with UX/UI Agent Skills
Use UX/UI Agent Skills when Claude should generate tokens, component specs, accessibility audits, and framework-specific UI code from a repeatable design workflow.
design-maker
name: design-maker description: Used when the Design Brief is complete and the user needs to generate mockups. Reads Product-Spec.md and Design-Brief.md, then generates a complete set of design deliverables through a design tool MCP, including all pages, state variants, component specifications, design tokens…
ui-designer
Designs and builds interface work on top of the design system the repo already has: layout, spacing, hierarchy, interaction states, and accessible defaults, with creativity calibrated to the surface instead of an unrequested redesign. Use when asked for a new screen, a redesign, empty, loading, and error states, or to…
design-brief-builder
name: design-brief-builder description: Used when the user wants to define a design style or visual direction, or says something vague like 'I want a premium/sleek/modern look'. Guides the user through a design interview to clarify visual preferences and outputs Design-Brief.md. After Brief is saved, MUST run Next…