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 Kevin-Liu-01/Sigil-UI --skill sigil-migrationgit clone --depth 1 https://github.com/Kevin-Liu-01/Sigil-UIWrote 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/kevin-liu-01/sigil-ui/sigil-migration)<a href="https://agentmods.dev/skills/kevin-liu-01/sigil-ui/sigil-migration"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/sigil-ui/sigil-migration/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/kevin-liu-01/sigil-ui/sigil-migration"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/sigil-ui/sigil-migration.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.00004 | $0.01819 |
| Opus 5 | $0.00002 | $0.00910 |
| Sonnet 5 | $0.00001 | $0.00364 |
| Haiku 4.5 | $0.00000 | $0.00182 |
Grade A, and why
sigil-migration 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sigil Migration
Migrate a project from shadcn/ui to Sigil UI while preserving functionality and improving design coherence.
When to Use
- User asks to migrate from shadcn to Sigil
- User says "replace shadcn", "switch to sigil", "migrate"
- User has a shadcn-based project and wants Sigil's token system
- User wants to gradually adopt Sigil alongside existing shadcn components
How to Use
1. Assessment
Before migrating, audit the existing project:
# Count shadcn components in use
ls src/components/ui/
# Check for shadcn config
cat components.json
# Find all shadcn token references (cn, cva, class-variance-authority)
rg "from.*class-variance-authority" --files-with-matches
rg "from.*@/lib/utils" --files-with-matches
2. Migration strategy
Choose one:
A. Full swap — replace all shadcn components at once. Best for small projects (<10 components).
B. Incremental — migrate one component at a time. Both systems coexist. Best for large projects.
C. Tokens-only — keep shadcn components but replace the CSS variable layer with Sigil tokens. Fastest path.
3. Token mapping
Map shadcn CSS variables to Sigil equivalents:
| shadcn variable | Sigil variable |
|---|---|
--background |
--s-background-light/dark |
--foreground |
--s-text-light/dark |
--card |
--s-surface-light/dark |
--card-foreground |
--s-text-light/dark |
--primary |
--s-primary |
--primary-foreground |
(compute: white/black based on L) |
--secondary |
--s-secondary |
--muted |
--s-surface-light/dark |
--muted-foreground |
--s-text-muted-light/dark |
--accent |
--s-primary-muted |
--destructive |
--s-error |
--border |
--s-border-light/dark |
--input |
--s-border-light/dark |
--ring |
--s-border-interactive |
--radius |
--s-radius-md |
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 · 223 lines · 4 tokens per session scan A 1ea9869bf468
sigil-migration is a skill published in the GitHub repository Kevin-Liu-01/Sigil-UI (9 stars, last pushed 1mo ago), licensed MIT. It adds 4 tokens to every session and 1,819 once invoked, about $0.0000 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
ss-studio
Turn a product brief and optional references into three distinct creative directions, a human-selected StyleSeed interaction plan, generated image/video asset jobs, a working UI prototype, and a verified prototype-first showcase reel. Use for client concepts, app interaction exploration, trendy but coherent UI…
ss-lint
Quick automated lint — detects common design system violations in seconds.
ss-a11y
Audit a component or page for accessibility issues and fix them.
ss-copy
Generate UX microcopy (button labels, error messages, empty states, toasts) following a casual-but-polite voice and tone.
ss-audit
Audit screens for UX issues using Nielsen's heuristics and modern mobile UX best practices.
ss-flow
Design user flows and navigation structure following proven UX patterns.