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 GlamgarOnDiscord/claude-saas-blueprint --skill variationsgit clone --depth 1 https://github.com/GlamgarOnDiscord/claude-saas-blueprintWrote 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/glamgarondiscord/claude-saas-blueprint/variations)<a href="https://agentmods.dev/skills/glamgarondiscord/claude-saas-blueprint/variations"><img src="https://agentmods.dev/badge/skills/glamgarondiscord/claude-saas-blueprint/variations/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/glamgarondiscord/claude-saas-blueprint/variations"><img src="https://agentmods.dev/badge/skills/glamgarondiscord/claude-saas-blueprint/variations.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.00044 | $0.00705 |
| Opus 5 | $0.00022 | $0.00352 |
| Sonnet 5 | $0.00009 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
variations 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 11d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arguments
component: Quel composant ou quelle page à explorercount: Nombre de variations (défaut: 5, max: 10)
Instructions
1. Comprendre le Composant
- Lire le composant existant (si il existe)
- Identifier les props, le data model, les contraintes
- Lire le design system en place (shadcn, tailwind config, etc.)
2. Planifier les Variations
Avant de coder, lister les approches UX différentes. Exemples :
- Layout : Cards grid vs Table vs List vs Kanban vs Timeline
- Navigation : Tabs vs Accordion vs Wizard vs Split view vs Sidebar
- Interaction : Modal vs Inline edit vs Drawer vs Full page vs Popover
- Densité : Compact vs Comfortable vs Spacious
- Style : Minimal vs Rich vs Glassmorphism vs Brutalist
Chaque variation doit être fondamentalement différente en approche UX, pas juste une variation de couleur.
3. Générer les Fichiers
Créer un dossier temporaire :
src/components/_variations/
├── [component]-v1-cards-grid.tsx
├── [component]-v2-table-view.tsx
├── [component]-v3-kanban.tsx
├── [component]-v4-timeline.tsx
├── [component]-v5-split-view.tsx
└── _preview.tsx ← Page qui affiche toutes les variations
Le fichier _preview.tsx :
// Page de preview — accéder via /variations ou route temporaire
// Affiche toutes les variations côte à côte ou en tabs
// Avec des données mock réalistes
4. Chaque Variation Doit
- Être un composant standalone fonctionnel
- Utiliser les mêmes props/données
- Avoir un titre visible indiquant le concept (ex: "V3 — Kanban Board")
- Être responsive
- Utiliser shadcn/ui et Tailwind
5. Présentation
Informer l'utilisateur :
5 variations générées dans src/components/_variations/
Ouvre [URL preview] pour les comparer visuellement.
V1 — Cards Grid : Layout classique en grille de cartes
V2 — Table View : Vue tabulaire dense avec tri et filtres
V3 — Kanban : Vue en colonnes draggable
V4 — Timeline : Vue chronologique verticale
V5 — Split View : Master-detail avec panneau latéral
Dis-moi laquelle tu préfères (ou un mix), et je supprime le reste.
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.
- 11d ago First seen · 74 lines · 44 tokens per session scan A b1a59c216867
variations is a skill published in the GitHub repository GlamgarOnDiscord/claude-saas-blueprint (2 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 705 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-31.
Other skills, from other repositories
tailwind-design-system
Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
motion-graphics
Use when the user wants a short, design-led motion graphic where motion is the message: kinetic typography, stat or number count-up, chart/data-viz hit, logo sting, brand lockup, lower-third, callout, social overlay, animated headline/tweet/news item, motion poster, or quick captured-page highlight. Usually under 10s…
visual-style
Create, extract, and apply portable visual design systems via visual-style.md files. Use when: (1) Creating a visual-style.md design system from scratch, (2) Extracting a visual style from a website URL, video, or PDF brand guide, (3) Applying a visual style to HeyGen videos, HTML slides, Figma, or paper.design, (4)…
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
apply-mantel-styles
Provides guidelines for applying Mantel's brand styles to diagrams and frontend components. Use when asked to create visuals that need to align with Mantel's branding.