Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/marcusgoll/Spec-Flownpx agentmods add commands/marcusgoll/spec-flow/init-tokensWrote 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/commands/marcusgoll/spec-flow/init-tokens)<a href="https://agentmods.dev/commands/marcusgoll/spec-flow/init-tokens"><img src="https://agentmods.dev/badge/commands/marcusgoll/spec-flow/init-tokens/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/commands/marcusgoll/spec-flow/init-tokens"><img src="https://agentmods.dev/badge/commands/marcusgoll/spec-flow/init-tokens.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.00000 | $0.05270 |
| Opus 5.5 | $0.00000 | $0.02108 |
| Sonnet 5.5 | $0.00000 | $0.01054 |
| Haiku 4.5 | $0.00000 | $0.00527 |
Grade A, and why
init-brand-tokens 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.
How it starts
The opening of the file, as written. The whole thing — 585 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/init-brand-tokens — Design System Token Generation
Existing Tokens: !test -f design/systems/tokens.json && echo "exists" || echo "missing"
Tailwind Config: !test -f tailwind.config.js && echo "found (js)" || test -f tailwind.config.ts && echo "found (ts)" || echo "missing"
Node Version: !node --version 2>/dev/null || echo "not installed"
Project Mode: !test -d app -o -d src -o -d components && echo "brownfield (UI exists)" || echo "greenfield (new project)"
Reference Documentation: @.claude/skills/design-tokens/SKILL.md
Modes:
- Brownfield: Scan existing code (UI, emails, PDFs, CLI, charts, docs) for color/type/spacing patterns, consolidate duplicates
- Greenfield: Ask 8 customization questions, generate new OKLCH palette with semantic tokens + shadcn integration
- From Prototype (--from-prototype): Extract and formalize colors from discovery prototype's theme.yaml
- shadcn Integration (--shadcn): Generate shadcn/ui-compatible configuration alongside OKLCH tokens
When to use:
- During
/init-project, before first/design - After
/prototype discoverto formalize quick-picked palette - When migrating ad-hoc styles to systematic tokens
- When setting up shadcn/ui components with custom theming
Surfaces covered: UI components, MJML/HTML emails, PDF styling, CLI colors, data viz, docs, discovery prototypes, shadcn/ui components
Anti-Hallucination Rules
- Never run script without checking dependencies
- Verify Node.js installed with
node --version - Check colorjs.io, picocolors, fs-extra in package.json
- If missing, install with:
pnpm add -D colorjs.io picocolors fs-extra
- Verify Node.js installed with
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 · 585 lines · 0 tokens per session scan A 5988580e2813
init-brand-tokens is a command published in the GitHub repository marcusgoll/Spec-Flow (96 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,270 tokens. 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-30.
Other commands, from other repositories
ux-recommend
The v2 flagship. Runs the 5-parallel-search Python engine across 11 data manifests (75+ styles, 170+ palettes, 65+ type pairs, 120+ components, 170+ industries, 110+ UX laws, 50+ motion presets, 120+ anti-patterns, 92 brand specs) and returns a complete recommended design system for your project — with always-on…
color-specialist
Use when colour is failing. Contrast below AA, a palette with no system behind it, dark mode that is only inverted light mode, or semantic colours that carry no meaning.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
revisar-ui
Auditoria visual retroativa de 6 pilares do código frontend implementado.
bolder
Read and follow the instructions in agents/skills/bolder.md. Also read and follow agents/frontend-design/design-all.md and any referenced files in agents/frontend-design/reference/ as needed.
colorize
Introduce or rework color strategy.