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 skills/dragoon0x/canon/canon-responsivenpx skills add Dragoon0x/canon --skill canon-responsivegit 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-responsive)<a href="https://agentmods.dev/skills/dragoon0x/canon/canon-responsive"><img src="https://agentmods.dev/badge/skills/dragoon0x/canon/canon-responsive.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.00061 | $0.02273 |
| Opus 5 | $0.00030 | $0.01137 |
| Sonnet 5 | $0.00012 | $0.00455 |
| Haiku 4.5 | $0.00006 | $0.00227 |
Grade A, and why
canon-responsive 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CANON · Responsive Design
Mobile-first is non-negotiable. Container queries beat media queries for component-level responsiveness. Fluid type beats stepped breakpoints for headings.
Quantified Rules
Breakpoints
/* Mobile-first: base styles target the smallest screen */
/* Default: < 640px */
@media (min-width: 640px) { /* sm — large phone, small tablet */ }
@media (min-width: 768px) { /* md — tablet portrait */ }
@media (min-width: 1024px) { /* lg — tablet landscape, small laptop */ }
@media (min-width: 1280px) { /* xl — laptop */ }
@media (min-width: 1536px) { /* 2xl — large desktop */ }
These match Tailwind defaults and align with common device widths. Don't invent breakpoints unless the design demands it.
Use min-width, not max-width. Mobile-first means base styles work everywhere, breakpoints add complexity at larger sizes.
Container Widths
| Container | Mobile (<640) | Tablet (768) | Desktop (1280+) |
|---|---|---|---|
| Page horizontal padding | 16–24px | 32–48px | 48–80px |
| Prose max-width | 100% | 65ch | 65ch |
| Marketing max-width | 100% | 100% | 1200–1280px |
| App max-width | 100% | 100% | 1440–1600px |
Fluid Type
Use clamp() for headings that scale smoothly between mobile and desktop:
h1 {
font-size: clamp(2rem, 5vw + 1rem, 4.5rem);
/* min, preferred, max */
}
| Heading | Fluid range |
|---|---|
| H1 (marketing) | clamp(2rem, 5vw + 1rem, 4.5rem) (32–72px) |
| H1 (app) | clamp(1.75rem, 3vw + 0.5rem, 2.25rem) (28–36px) |
| H2 | clamp(1.5rem, 3vw + 0.5rem, 2.25rem) (24–36px) |
| H3 | clamp(1.25rem, 2vw + 0.5rem, 1.75rem) (20–28px) |
| Body | 16px (don't scale body) |
Rule: scale headings, not body text. Body stays 16px across all sizes for reading consistency.
Container Queries (preferred over media for components)
.card-grid {
container-type: inline-size;
}
.card {
/* default: 1 column */
display: block;
}
@container (min-width: 600px) {
.card {
display: grid;
grid-template-columns: 200px 1fr;
}
}
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 · 261 lines · 61 tokens per session scan A c96012e73bf3
canon-responsive is a skill published in the GitHub repository Dragoon0x/canon (5 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 2,273 once invoked, about $0.0003 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
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
Fast, high-signal accessibility triage for pages, components, or PRs targeting WCAG 2.2 AA compliance.
token-architecture
Design token architecture — multi-tier token systems, semantic naming, theme switching, CSS custom properties, Tailwind mapping, and Figma variable sync.
memoire-design-tooling
Set up and operate Mémoire's CLI, MCP server, agent kits, design preflight, UX audits, craft checks, tokens, and registry evidence. Use when a repository explicitly needs Mémoire tooling; use portable design skills when Mémoire is unavailable.
swiftui-layout-components
Build SwiftUI layouts using stacks, grids, lists, scroll views, forms, and controls. Covers VStack/HStack/ZStack, LazyVGrid/LazyHGrid, List with sections and swipe actions, ScrollView with ScrollPosition and scroll-driven reveal surfaces, Form with validation, Toggle/Picker/Slider, .searchable, and overlay patterns.…
better-typography
Web typography from choosing fonts to spacing, wrapping and accessibility. Use when picking or pairing typefaces, configuring variable fonts or OpenType features, setting up a type scale, checking heading hierarchy, styling text in components, truncating text, styling underlines, selection, placeholders or carets, or…