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 skills add Dragoon0x/canon --skill canon-badgesgit 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/skills/dragoon0x/canon/canon-badges)<a href="https://agentmods.dev/skills/dragoon0x/canon/canon-badges"><img src="https://agentmods.dev/badge/skills/dragoon0x/canon/canon-badges/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/skills/dragoon0x/canon/canon-badges"><img src="https://agentmods.dev/badge/skills/dragoon0x/canon/canon-badges.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.00103 | $0.02066 |
| Opus 5.5 | $0.00041 | $0.00826 |
| Sonnet 5.5 | $0.00021 | $0.00413 |
| Haiku 4.5 | $0.00010 | $0.00207 |
Grade A, and why
canon-badges 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 2mo 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CANON · Badges
Small metadata shapes. Badges, chips, pills, and tags are all adjacent concepts; the right name matters less than the right behavior.
What belongs in a badge
| Appropriate | Not appropriate |
|---|---|
| Status ("Active", "Draft") | Full sentences |
| Count (3, 99+) | Paragraph-length content |
| Category or tag (frontend, urgent) | Primary actions |
| Labels on entities (beta, new) | Navigation links |
| Version numbers ("v2.1") | Buttons |
Badges are metadata. If users click a badge and something changes, they expected a button.
Badges vs chips vs tags
| Pattern | Interactive? | Use |
|---|---|---|
| Badge | Usually no | Display-only metadata (status, count, version) |
| Chip | Yes | Selected filters, removable tokens, multi-select |
| Tag | Optional | Categorization; either display or selectable |
| Notification dot | No | Unseen-items indicator |
Most are the same visual shape (rounded rectangle) but different behavior. Don't make display-only badges look clickable — confuses users.
Sizing
| Size | Height | Padding | Font |
|---|---|---|---|
| XS | 16–18px | 4–6px horizontal | 10–11px |
| SM | 20px | 6–8px | 11–12px |
| MD | 24px | 8–10px | 12–13px |
| LG | 28–32px | 10–14px | 13–14px |
Most UI badges are SM or MD. XS only for dense tables and inline markers.
Border radius: 4–6px for rectangular feel, 999px for pill. Stay consistent within a UI.
Color coding — status conventions
Users learn color semantics. Respect the conventions.
| Intent | Color | Examples |
|---|---|---|
| Success / active | Green | "Published", "Active", "Online" |
| Info / neutral | Blue or gray | "Draft", "New", "Info" |
| Warning | Yellow / amber | "Expiring soon", "Review needed" |
| Danger / error | Red | "Failed", "Overdue", "Blocked" |
| Muted / inactive | Gray | "Archived", "Inactive" |
Color alone is never the only signal. Pair with the label text. WCAG 1.4.1.
Tonal badges (preferred)
Instead of saturated-fill badges (loud), use tonal:
- Light background (10–15% of the hue's lightness zone) +
- Dark text (60–70% of the hue's lightness zone).
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.
- 2mo ago First seen · 245 lines · 103 tokens per session scan A 0cbef7529754
canon-badges is a skill published in the GitHub repository Dragoon0x/canon (6 stars, last pushed 6mo ago), licensed MIT. It adds 103 tokens to every session and 2,066 once invoked, about $0.0004 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.
canon-badges compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| canon-badgesDragoon0x/canon | Skill | 6 | 6mo ago | MIT | A | 103 | Claude Code, Codex |
| accessibilitydiegosouzapw/awesome-omni-skills | Skill | 170 | 4mo ago | MIT | C | 119 | Claude Code, Codex |
| accessibilityericrisco/rsc-harness | Skill | 503 | 2d ago | MIT | A | 86 | Claude Code, Codex |
| accessibility-auditoyi77/1ai-skills | Skill | 17 | yesterday | MIT | A | 29 | Claude Code |
| a11y-auditgreglas75/zuvo | Skill | 7 | 3d ago | MIT | A | 147 | Claude Code |
| axe-audittonone-ai/tonone | Skill | 77 | 23d ago | MIT | A | 47 | Claude Code |
| accessibility-compliance-accessibility-audit-v2diegosouzapw/awesome-omni-skills | Skill | 170 | 4mo ago | MIT | A | 76 | Claude Code |