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-modalsgit 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-modals)<a href="https://agentmods.dev/skills/dragoon0x/canon/canon-modals"><img src="https://agentmods.dev/badge/skills/dragoon0x/canon/canon-modals/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-modals"><img src="https://agentmods.dev/badge/skills/dragoon0x/canon/canon-modals.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.00084 | $0.01963 |
| Opus 5 | $0.00042 | $0.00981 |
| Sonnet 5 | $0.00017 | $0.00393 |
| Haiku 4.5 | $0.00008 | $0.00196 |
Grade A, and why
canon-modals 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 9d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CANON · Modals
A modal interrupts the user. Every modal should justify the interruption. Most shouldn't exist.
When to use a modal
| Use modal | Don't use modal |
|---|---|
| Confirming a destructive action with no undo | Confirming a reversible action (use Undo toast) |
| Focused task that requires full attention (image edit, payment) | Editing a field (inline edit) |
| Error or warning blocking progress | Informational messages (toast/banner) |
| Critical form that must complete before continuing | Forms that can live on a page |
| Collecting user input for current flow only | Secondary workflows (new tab/page) |
Undo beats confirm. A toast with "Item deleted. [Undo]" is almost always better than "Are you sure?"
Modal vs drawer vs popover vs sheet
| Pattern | Overlay | Blocks page | Anchored | Use |
|---|---|---|---|---|
| Modal dialog | Full | Yes | Center | Critical decisions, focused tasks |
| Drawer (side) | Partial | Yes | Edge | Settings panels, filters, nav |
| Popover | None | No | Element | Supplemental info, small forms |
| Bottom sheet (mobile) | Partial | Yes | Bottom | Mobile primary pattern for drawers |
| Fullscreen sheet (mobile) | Full | Yes | Full | Complex mobile tasks |
Use the <dialog> element
Native <dialog> handles focus trap, ESC, backdrop, and scroll lock for free. Stop reinventing it.
<dialog id="confirm-delete">
<h2>Delete project?</h2>
<p>This permanently removes the project and all 47 files.</p>
<div class="actions">
<button value="cancel">Cancel</button>
<button value="confirm" class="destructive">Delete project</button>
</div>
</dialog>
<script>
const dialog = document.getElementById('confirm-delete');
dialog.showModal(); // Modal with backdrop + focus trap
// dialog.show(); // Non-modal
</script>
If you must build without <dialog>, the requirements below are non-negotiable.
Required behaviors
- Focus moves into the dialog on open. The first focusable element, or the most useful (e.g., the primary action).
- Focus trapped inside. Tab and Shift+Tab cycle within. Nothing outside is reachable.
- Focus returns to trigger on close. The element that opened the modal gets focus back.
- Escape closes. Unless explicitly forbidden (rare).
- Click outside closes. For non-critical modals. For critical confirmations, require explicit button press.
- Scroll locked on body. No scrolling behind the modal.
overflow: hiddenon<html>, not<body>— that loses scroll position on mobile Safari. - Backdrop visible. 40–60% opacity black or tinted dark with blur for modern feel.
role="dialog"orrole="alertdialog". Alertdialog for critical confirmations.aria-labelledbypointing to the heading. Oraria-labelif no visible heading.
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.
- 9d ago First seen · 197 lines · 84 tokens per session scan A 548c065ca436
canon-modals is a skill published in the GitHub repository Dragoon0x/canon (5 stars, last pushed 4mo ago), licensed MIT. It adds 84 tokens to every session and 1,963 once invoked, about $0.0004 per session on Opus 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 skills, from other repositories
accessibility
Accessibility (a11y) workflow skill. Use this skill when the user needs Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible". Do NOT use for SEO (use seo)…
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…
accessibility-audit
Use when wCAG compliance audit — semantic HTML, ARIA, keyboard navigation, color contrast, and screen reader testing. Use when working with accessibility audit.
token-architecture
Design token architecture — multi-tier token systems, semantic naming, theme switching, CSS custom properties, Tailwind mapping, and Figma variable sync.
figma-generate-library
Generate Figma component library from React/shadcn codebase with Code Connect parity.
figma-sync
Figma sync workflow patterns — bidirectional design-code sync, conflict resolution, incremental updates, multi-file orchestration.