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-componentgit 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-component)<a href="https://agentmods.dev/skills/kevin-liu-01/sigil-ui/sigil-component"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/sigil-ui/sigil-component/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-component"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/sigil-ui/sigil-component.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.00003 | $0.01117 |
| Opus 5 | $0.00002 | $0.00558 |
| Sonnet 5 | $0.00001 | $0.00223 |
| Haiku 4.5 | $0.00000 | $0.00112 |
Grade A, and why
sigil-component 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sigil Component
Create and modify React components that consume Sigil design tokens via CSS custom properties.
When to Use
- User asks to create a new Sigil UI component
- User asks to modify an existing component in
packages/components/ - User says "add a component", "create component", "build a button/card/input"
- User asks to style a component using Sigil tokens
- User wants to add a component to the CLI registry
How to Use
1. Understand the component structure
Every Sigil component lives in packages/components/src/ and follows this pattern:
import { forwardRef, type ComponentPropsWithoutRef } from "react";
import { clsx } from "clsx";
type ButtonProps = ComponentPropsWithoutRef<"button"> & {
variant?: "default" | "outline" | "ghost";
size?: "sm" | "md" | "lg";
};
export const Button = forwardRef<HTMLButtonElement, ButtonProps>(
({ className, variant = "default", size = "md", children, ...props }, ref) => {
return (
<button
ref={ref}
className={clsx(
"sigil-button",
`sigil-button--${variant}`,
`sigil-button--${size}`,
className,
)}
{...props}
>
{children}
</button>
);
},
);
Button.displayName = "Button";
2. Token consumption rules
Components consume tokens exclusively through CSS custom properties. Never hardcode colors, spacing, or typography values.
.sigil-button {
font-family: var(--s-font-body);
background: var(--s-primary);
color: var(--s-text-light);
border-radius: var(--s-radius-md);
padding: var(--s-spacing-2) var(--s-spacing-4);
box-shadow: var(--s-shadow-sm);
transition-duration: var(--s-duration-fast);
transition-timing-function: var(--s-easing-default);
}
3. Register in CLI
After creating a component, add it to packages/cli/src/utils/registry.ts:
"my-component": {
name: "my-component",
files: ["my-component.tsx"],
dependencies: [], // npm deps like @radix-ui/*
devDependencies: [],
registryDependencies: [], // other sigil components this depends on
},
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 · 153 lines · 3 tokens per session scan A 5d41d93dee72
sigil-component is a skill published in the GitHub repository Kevin-Liu-01/Sigil-UI (9 stars, last pushed 1mo ago), licensed MIT. It adds 3 tokens to every session and 1,117 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.