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 agentmods add commands/alwkala/tidyfactor-design/brandgit 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/brand)<a href="https://agentmods.dev/commands/alwkala/tidyfactor-design/brand"><img src="https://agentmods.dev/badge/commands/alwkala/tidyfactor-design/brand.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.01099 |
| Opus 5 | $0.00000 | $0.00549 |
| Sonnet 5 | $0.00000 | $0.00220 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
brand 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 5d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: brand — Brand Identity Scaffolding & Extraction
Runtime entry point for creating, extracting, or evolving brand.json v2. Part of the Foundation lifecycle phase.
When to use
- New project → scaffold
brand.jsonfrom scratch with user interview - Existing identity → extract
brand.jsonfrom a live site, PDF guidelines, or logo + reference photos (theclone-brandpath) - Schema upgrade → migrate
brand.jsonv1 to v2
Dispatch Steps
- Load
memory/11-brand-json-v2.md— full schema reference. - Load
memory/02-design-tokens.md— token derivation rules. - Determine path: scaffold (no existing identity) or extract (existing site/PDF/assets).
- Execute the appropriate protocol below.
Path A: Scaffold (new identity)
Interview (ask these in order)
- Product name + tagline →
meta.product,meta.tagline - Logo files →
identity.logo.*(SVG preferred; if unavailable, flag as missing — do NOT fabricate) - Primary color + accent → seed
colors.light.primary,colors.light.accent - Light or dark default? → determines which mode's
background/surface/textvalues are set first - Voice/tone →
voice.tone,voice.personality(3 adjectives) - Foundation →
foundation(one of 8 supported options) - Design school →
school(one of the movements inmemory/01-design-schools.md) - Locales →
localization.supportedLocales,localization.rtl
Auto-derived tokens
From the primary color + mode choice, auto-generate:
primaryForeground(contrast-safe white or dark)secondary(complementary hue shift)surface,surface2,border(tinted neutrals — NEVER pure black/white)- Dark mode mirror tokens (shift lightness, preserve hue)
shadows.focusRingusingcolor-mix()from the primary
Path B: Extract (existing identity → brand.json)
What to extract, and from where
| Token | Primary source | Fallback |
|---|---|---|
colors.* |
Computed styles of existing site's key surfaces (buttons, header bg, body text) — sample actual rendered hex, NOT guesses from screenshots | Ask user for 2–3 hex values |
typography.families.* |
<link>/@font-face declarations in HTML/CSS |
Route through memory/12-typography-matrix.md mood table |
voice.* |
Read 3–5 paragraphs of existing marketing copy; infer register | Ask user for 3 adjectives |
identity.logo.* |
Existing logo file (SVG or high-res PNG with transparency) | Flag as missing — do NOT fabricate |
localization.* |
<html lang> / dir on existing site |
Ask which locales needed |
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.
- 5d ago First seen · 86 lines · 0 tokens per session scan A 3c968e850fbb
brand 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 1,099 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
github-issue
Create a GitHub issue from a natural language description.
test
Hello world test command.
critique-screen
Run all seven visual critiques on a screen and output a prioritised fix list.
critique-ux
Run a focused UX critique on a screen — affordances, information density, and hierarchy — and output a prioritised fix list.
design-onboarding
Design a first-run experience end to end — activation path, progressive disclosure, and time to first value.
frame-problem
Structure an ambiguous design challenge into a clear problem definition with constraints and criteria.