Borrowing it
Nothing to install: this file belongs to alwkala/tidyfactor-design. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/alwkala/tidyfactor-design/main/.agents/skills/tidyfactor-design/references/commands/tokens.mdgit clone --depth 1 https://github.com/alwkala/tidyfactor-designWrote 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/alwkala/tidyfactor-design/tokens)<a href="https://agentmods.dev/commands/alwkala/tidyfactor-design/tokens"><img src="https://agentmods.dev/badge/commands/alwkala/tidyfactor-design/tokens.svg" alt="Measured on agentmods" 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.00522 |
| Opus 5 | $0.00000 | $0.00261 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: tokens — Design Tokens & brand.json
Purpose
Establish the single source of truth every other command reads from. This is the one command every later command depends on — re-running it (a rebrand, a palette fix) is how a change propagates to every page at once.
When to run it
- Start of
init— always first, right afterschool. - The user says "update the brand colors", "adjust the type scale",
"we rebranded",
tokens.
What it does
- Derive token categories from the
schooldecision and brief:colors— primary/secondary/accent + light/dark surface scalestypography— display/body/mono families, a type scale (not arbitrary per-heading sizes), weightsspacing— a consistent scale (e.g. 4px base), not ad hoc valuesradius,shadow— a small fixed set, not one-off values per componentmotion— duration/easing tokens (feedsmotioncommand)
- Write
design-system/tokens.cssas:rootcustom properties (Native/ Hybrid), or the equivalent theme-config object (Tailwind), or the[data-theme]block (daisyUI) — perreferences/foundations/<choice>.md. - Write/update
design-system/brand.json:meta.*,colors.*,typography.*,spacing.*,voice.*(copy tone/register),cssFoundation,localization.*(default locale, RTL locales — seei18n). - If tokens.css already exists and pages already reference it: this is a propagating change — flag every existing page for re-verification after the update, don't silently assume they still look correct.
Output convention
design-system/
tokens.css ← :root custom properties (or foundation-equivalent)
brand.json ← structured source; tokens.css is generated to match it
Checklist
- Every token category present: colors, typography, spacing, radius, shadow, motion
-
cssFoundationrecorded inbrand.jsonand matches the project's actual<head>includes - If tokens changed on an existing project, affected pages flagged for re-verification
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 · 46 lines · 0 tokens per session scan A 359b5ccfe7b8
tokens is a command published in the GitHub repository alwkala/tidyfactor-design (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 522 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-31.
Other commands, from other repositories
start-here
Find where to start in the collection — name what you're working on and get routed to one command, the two that follow it, and the stages you can skip.
critique-screen
Run all seven visual critiques on a screen and output a prioritised fix list.
explore-options
Run a parallel exploration end to end — frame the decision, build a spread of behaviourally distinct concepts, pressure-test each, and converge with a decision record.
platform-audit
Audit a design for iOS and Android convention compliance — navigation, controls, typography, and platform-specific gaps.
critique-ux
Run a focused UX critique on a screen — affordances, information density, and hierarchy — and output a prioritised fix list.
handoff
Run the full handoff workflow — specs, measurements, assets, states, and a QA checklist — and output a developer-ready package.