extract

A command that finds repeated design values in a codebase and gathers them into a shared tokens file. Design tokens are named values for things such as colors, spacing, fonts, corners, shadows, and animation timing.

In plain words
What is it for?
Use it to scan CSS, Tailwind settings, theme files, and inline styles, then produce normalized tokens and a migration plan.
Why use it?
It removes scattered and inconsistent styling values, making it easier to see duplicates and plan a cleanup.

Command

Install

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.

agentmods
npx agentmods add commands/dragoon0x/canon/extract
Clone the repo
git clone --depth 1 https://github.com/Dragoon0x/canon
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 476 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00476
Opus 5 $0.00010 $0.00238
Sonnet 5 $0.00004 $0.00095
Haiku 4.5 $0.00002 $0.00048

Measured 2d ago against content hash ae061de2a73f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

extract 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 2d 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.

source/commands/extract.md · 41 lines

What it actually says

/extract

Walk a codebase, find every color, spacing, font, radius, and shadow value, and consolidate them into a single token layer.

What this does

  1. Scan the codebase (CSS, Tailwind configs, theme files, inline styles).
  2. Categorize findings:
    • Colors: hex, rgb, hsl, oklch. Group by perceptual similarity.
    • Spacing: every margin, padding, gap. Map to nearest 4px/8px grid value.
    • Typography: font-size, line-height, font-weight, letter-spacing. Map to the nearest modular-scale step.
    • Radii: border-radius values.
    • Shadows: box-shadow strings.
    • Timing: transition durations and easings.
  3. Detect inconsistencies:
    • "We have 7 grays that are perceptually the same" → collapse to 1.
    • "Spacing includes 10px, 11px, 13px, 15px — none on the grid" → snap to nearest.
    • "5 shades of blue used as 'primary'" → pick canonical, flag rest.
  4. Apply canon-color, canon-typography, canon-spatial as the normalization target.
  5. Build the token file in three layers:
    • Primitive: raw scale (--blue-500, --space-4).
    • Semantic: intent (--color-brand-primary, --gap-card).
    • Component: contextual (--button-primary-bg).
  6. Output a migration plan: old value → new token, per file.

Output

  • Token file (tokens.css or tokens.js).
  • Consolidation report: X colors → Y tokens, with rationale.
  • Migration map: file-by-file search/replace list.
  • Inconsistencies flagged (spacing off-grid, contrast failures introduced).

Success criteria

Every raw value in the codebase either becomes a token or is flagged as off-system. Token count drops significantly (typical result: 40–70% reduction). Nothing visually breaks.

Changes

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.

  1. 2d ago First seen · 41 lines · 20 tokens per session scan A ae061de2a73f

Subscribe to this mod's changes

extract is a command published in the GitHub repository Dragoon0x/canon (5 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 476 once invoked, about $0.0001 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.