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.
git clone --depth 1 https://github.com/Dragoon0x/canonWrote 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/dragoon0x/canon/colorize)<a href="https://agentmods.dev/commands/dragoon0x/canon/colorize"><img src="https://agentmods.dev/badge/commands/dragoon0x/canon/colorize/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/dragoon0x/canon/colorize"><img src="https://agentmods.dev/badge/commands/dragoon0x/canon/colorize.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.00021 | $0.00507 |
| Opus 5.5 | $0.00008 | $0.00203 |
| Sonnet 5.5 | $0.00004 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
colorize 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.
What it actually says
/colorize
Construct a color system, or audit an existing one. Not "pick pretty colors" — perceptual scales, contrast math, semantic layering.
What this does
- Load
canon-color. - Work in OKLCH. Hex is fine for final output; reasoning happens in OKLCH.
- Build the base palette:
- Neutrals: 10–12 step tinted ramp. Never
#000000or#ffffffas the extremes. Start at L=7–10% and end at L=96–99%. Add 2–5% chroma toward the brand hue to avoid dead gray. - Brand: full 10-step ramp, L=15% to L=95%, chroma following the curve (peaks near L=60%).
- Semantic: success, warning, danger, info. Each gets a 10-step ramp.
- Neutrals: 10–12 step tinted ramp. Never
- Layer into tokens:
- Primitive: raw scale values (
--blue-500). - Semantic: intent names (
--color-brand-primary,--color-text-default). - Component: contextual (
--button-primary-bg).
- Primitive: raw scale values (
- Enforce contrast:
- Body text on background: 4.5:1 minimum (WCAG AA).
- Large text (18pt+ or 14pt+ bold): 3:1.
- UI components and focus rings: 3:1.
- Disabled state: exempt but must look unmistakably disabled.
- Build dark mode by inverting lightness roles, not by shifting hues. Text that was L=10% in light becomes L=90% in dark.
- Banned pairings:
- Gray text on a color (always fails contrast at light grays).
- Pure black shadows (use tinted neutral darkest).
- Red/green as the only signal for status.
Output
- OKLCH source definitions.
- Hex fallbacks.
- CSS custom properties for all three layers.
- Contrast audit table for critical pairings.
- Light and dark mode declarations.
Success criteria
Every semantic pair passes WCAG AA. No token uses a raw hex outside the primitive layer. Dark mode isn't a hue shift; it's a lightness inversion.
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 · 44 lines · 21 tokens per session scan A a85b542e385b
colorize is a command published in the GitHub repository Dragoon0x/canon (6 stars, last pushed 6mo ago), licensed MIT. It adds 21 tokens to every session and 507 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
agentation-fix
Session-2 fix loop for Agentation — read structured annotations from the dev overlay and apply targeted UI fixes.
scan-ai-tells
Scan UI or marketing copy for AI-default tells and content-authenticity misses — deletion list, not a redesign brief.
ccc-theme
List, preview or switch the Commander terminal color theme (Claude, OLED Black, Matrix, or a random palette) used by hooks and terminal art. Use when the user asks to change the theme, colors or skin.
extract-foundations-from-screens
Extract canonical foundations docs (color, typography, spacing, radii) from a batch of existing SCREENSPECs. Re-runs only add new tokens and route conflicts to a Review queue. Use when SCREENSPECs already document raw values and need converging into role tokens. Do not use when foundations are already curated and…
screen-spec
Generate a screen specification from a Figma frame using MCP tools (getdesigncontext, getscreenshot), matching the SCREENSPEC.md template (layout, states). Use when documenting a specific screen. Do not use when the screen has no Figma frame or the spec already exists, for 6 or more screens (use screen-spec-fleet), or…
design-critic
Use when you want an honest read on a design instead of encouragement. What is wrong, ranked by severity, with the reason attached. Works on a screenshot, a mockup, or a described screen.