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/audit)<a href="https://agentmods.dev/commands/dragoon0x/canon/audit"><img src="https://agentmods.dev/badge/commands/dragoon0x/canon/audit/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/audit"><img src="https://agentmods.dev/badge/commands/dragoon0x/canon/audit.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.00050 | $0.00707 |
| Opus 5.5 | $0.00020 | $0.00283 |
| Sonnet 5.5 | $0.00010 | $0.00141 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
audit 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit
Perform a full CANON audit of the current codebase or selection.
Process
Work through each CANON skill in order. For each, apply its Audit Checklist against the current interface. Record violations.
- canon-typography → font count, size scale, line-height, line length, Inter usage
- canon-color → contrast ratios, pure black/white, gray-on-color, token system
- canon-spatial → off-grid values, spacing scale count, touch targets
- canon-motion →
transition: all, hardcoded durations,prefers-reduced-motion, banned easings - canon-interaction → focus rings, hover treatment, disabled states, tap targets
- canon-responsive → mobile-first, container widths, fluid type, hover-wrapped
- canon-accessibility → semantic HTML, ARIA usage, keyboard, contrast, skip link
- canon-forms → labels, input types, autocomplete, validation timing, error specificity
- canon-depth → shadow construction, elevation tokens, z-index scale, border radius
- canon-states → 4 required states per screen, skeletons, error recovery
- canon-performance → LCP, INP, CLS, bundle size, image optimization
- canon-ux-writing → button labels, error messages, empty states, tone consistency
Output
Group findings by severity:
Critical (ship-blockers)
Accessibility violations (WCAG AA failures), broken interactions, data loss risks.
High (quality issues)
Inconsistent systems, off-scale values, missing states, anti-patterns.
Medium (polish)
Minor inconsistencies, optimization opportunities.
Low (nits)
Style preferences, subjective improvements.
For each finding, include:
- File and line where the issue lives
- What's wrong in one sentence
- Why it's wrong (reference to the CANON skill + cited standard)
- How to fix with a code diff where possible
Report Format
CANON AUDIT REPORT
==================
Repo: {name}
Date: {date}
Files: {count}
Score: {X}/100 ({critical} critical, {high} high, {medium} medium, {low} low)
CRITICAL
--------
1. [canon-accessibility] styles.css:42
Focus ring removed without replacement.
WCAG 2.4.7 violation.
Fix:
- outline: none;
+ &:focus-visible { outline: 2px solid var(--color-focus); outline-offset: 2px; }
2. [canon-color] Header.tsx:18
Body text #666 on #999 surface fails contrast (2.8:1, need 4.5:1).
WCAG 1.4.3 violation.
Fix: use var(--color-text) on var(--color-bg), check pair.
...
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 · 77 lines · 50 tokens per session scan A ae9a7a084d74
audit is a command published in the GitHub repository Dragoon0x/canon (6 stars, last pushed 6mo ago), licensed MIT. It adds 50 tokens to every session and 707 once invoked, about $0.0002 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.