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 scangit 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/scan)<a href="https://agentmods.dev/skills/dragoon0x/dragoon-skills/scan"><img src="https://agentmods.dev/badge/skills/dragoon0x/dragoon-skills/scan/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/scan"><img src="https://agentmods.dev/badge/skills/dragoon0x/dragoon-skills/scan.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.00116 | $0.00604 |
| Opus 5 | $0.00058 | $0.00302 |
| Sonnet 5 | $0.00023 | $0.00121 |
| Haiku 4.5 | $0.00012 | $0.00060 |
Grade A, and why
scan 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 8d 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
/scan
Generates dragoon.json, the canonical fingerprint of a codebase's design DNA. Every other dragoon skill reads or writes against this file.
When to use
Run /scan when:
- The user is setting up dragoon in a new project for the first time
- The user asks to "scan", "fingerprint", "audit the design system", "analyze the codebase"
- Another dragoon command (/critique, /slop, /review) needs a manifest and one doesn't exist
- The codebase has changed significantly and the existing manifest is stale
What it produces
A dragoon.json file at the project root with:
- stack: framework (react/next/vue/svelte/etc), styling layer (tailwind/css/styled-components/etc), language, package manager
- tokens.color: top distinct colors with usage counts and inferred roles
- tokens.spacing: distinct spacing values, inferred grid (4/6/8/12/16px), confidence score
- tokens.type: font families, font sizes, inferred scale ratio (golden, perfect-fourth, etc), confidence
- tokens.radius / shadow / motion / breakpoints: top values with counts
- metrics: file counts, component count estimate, accessibility signals (alt rate, button label rate, semantic tag use)
- rules: derived defaults (grid size, type ratio, max variants per token, allowed colors). Edit by hand if needed.
Run it
node ~/.claude/skills/dragoon/skills/scan/scripts/scan.js [root]
Flags:
--out <path>write to a custom path--jsonprint manifest to stdout--dry-runcompute but don't write--quietno terminal output beyond errors--helpfull usage
Notes
- Pure regex scanning. No AST parser dependency. No network calls.
- Skips node_modules, dist, build, .git automatically (gitignore-aware).
- Caps at 5,000 files per scan and 2MB per file. Larger codebases get a representative sample.
- Re-run /scan after major design changes to keep rules current.
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.
- 8d ago First seen · 49 lines · 116 tokens per session scan A 0b47d2390d73
scan is a skill published in the GitHub repository Dragoon0x/dragoon-skills (4 stars, last pushed 4mo ago), licensed MIT. It adds 116 tokens to every session and 604 once invoked, about $0.0006 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
design-system-tokens
Design token management with the W3C Design Token spec, three-tier hierarchy (global/alias/component), OKLCH color, Style Dictionary transforms, and dark mode theming. Use when creating token files, implementing theme systems, or building design-to-code pipelines.
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…
figma-export-tokens
Export Figma variables to design token files in DTCG, CSS custom properties, Tailwind v4/v3, SCSS, TypeScript, JSON, Style Dictionary, or Tokens Studio. Use when the user wants to pull design tokens OUT of Figma into code — triggers: 'export tokens', 'export Figma variables', 'generate CSS variables from Figma', 'turn…
figma-generate-component-doc
Generate complete Markdown documentation for a Figma component — anatomy/layer tree, design tokens (colors, spacing, typography), states/variants matrix, accessibility notes, content guidelines, and optional code-parity + YAML frontmatter. Use when the user wants a docs page or handoff spec for a component or…
figma-version-history
List a Figma file's version history, snapshot the file at any past version, and diff two versions (added/removed/renamed pages plus deep per-component changes). Use when the user wants to inspect Figma history — triggers: 'list Figma versions', 'what versions does this file have', 'show version history', 'snapshot…