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 Dragoon0x/dragoon-skills --skill componentgit clone --depth 1 https://github.com/Dragoon0x/dragoon-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/dragoon0x/dragoon-skills/component)<a href="https://agentmods.dev/skills/dragoon0x/dragoon-skills/component"><img src="https://agentmods.dev/badge/skills/dragoon0x/dragoon-skills/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/dragoon0x/dragoon-skills/component"><img src="https://agentmods.dev/badge/skills/dragoon0x/dragoon-skills/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.00112 | $0.00507 |
| Opus 5.5 | $0.00045 | $0.00203 |
| Sonnet 5.5 | $0.00022 | $0.00101 |
| Haiku 4.5 | $0.00011 | $0.00051 |
Grade A, and why
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 1mo 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.
What it actually says
/component
Generates a component scaffold that matches the codebase's existing style.
When to use
- The user asks to "create a component", "scaffold a UI primitive", "add a Card / Button / etc."
- The user wants a starting point that fits the existing design system
- Setting up a new feature that needs new UI
How it works
- Reads
dragoon.json(or runs /scan if missing) to detect the stack. - Picks a template based on framework + styling layer:
- react + tailwind → tsx with tailwind utility classes derived from your tokens
- react + css-modules → tsx + .module.css using your spacing grid and radius
- react + plain css → tsx + .css with kebab-case class
- vue → SFC with scoped styles
- svelte → .svelte single file
- Substitutes manifest tokens: spacing grid → padding, palette → bg/fg, radius scale → border-radius.
- Defaults to dry-run preview.
--applyactually writes files.
Run it
dragoon component <Name> [--dir path] [--apply]
# preview
dragoon component Card
# write to default src/components/
dragoon component Card --apply
# custom directory
dragoon component UserMenu --dir src/ui --apply
# overwrite existing
dragoon component Card --apply --overwrite
Safety
- Component name must be PascalCase identifier (rejects shell metacharacters, reserved words).
- Output directory is resolved inside the project root (rejects path traversal).
- Refuses to overwrite existing files unless
--overwriteis passed. - All writes are atomic (temp file + rename), so a failed write never leaves a half-written file.
What ships with it
1 file 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.
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.
- 1mo ago First seen · 53 lines · 112 tokens per session scan A 67c0edc16eca
component is a skill published in the GitHub repository Dragoon0x/dragoon-skills (4 stars, last pushed 6mo ago), licensed MIT. It adds 112 tokens to every session and 507 once invoked, about $0.0004 per session on Opus 5.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
Dark Mode Bug Finder
Detect dark mode rendering issues including contrast failures, missing theme tokens, image inversions, and transition glitches across components.
storefront-theming
Build a themeable storefront with design tokens and CSS custom properties that supports white-labeling, multi-brand variants, and dark mode.
accessible-by-default
Build web UI that is accessible through the platform instead of patched with ARIA and JavaScript. Use when writing or reviewing HTML and CSS for any web interface - choosing between a native element and a hand-built component, styling focus, honouring user preferences such as reduced motion or forced colors, meeting…
role-ui-ux-designer
Use when orchestrating UI/UX design systems, anti-AI-slop frontend styling, tactile micro-interactions, responsive design tokens, accessibility standards, and high-fidelity interface engineering.
figma-extract-design-system
Extract a design system from vibe-coded production apps that never had one: inventory components, mine de-facto styling into DTCG tokens, scaffold a Storybook package, port components, and optionally round-trip tokens/components into Figma. Use when the user wants to 'extract a design system', 'create a design system…
figma-blame-node
Find which Figma version introduced a specific change — a component property or a child node — via a binary search over version history (log2(N) API calls instead of N). Answers 'who added this and when'. Use when the user wants git-blame-style attribution for a Figma design — triggers: 'when was this component…