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-content-strategygit 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-content-strategy)<a href="https://agentmods.dev/skills/dragoon0x/canon/canon-content-strategy"><img src="https://agentmods.dev/badge/skills/dragoon0x/canon/canon-content-strategy/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-content-strategy"><img src="https://agentmods.dev/badge/skills/dragoon0x/canon/canon-content-strategy.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.00068 | $0.00742 |
| Opus 5 | $0.00034 | $0.00371 |
| Sonnet 5 | $0.00014 | $0.00148 |
| Haiku 4.5 | $0.00007 | $0.00074 |
Grade A, and why
canon-content-strategy 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 10d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CANON · Content Strategy
Design follows content. Not the other way around. Wireframing with "Lorem ipsum" produces layouts that break when real words arrive.
Content-first design
- Write the real content before the layout.
- Identify the hierarchy: what's the single most important thing on this page?
- Design the container around the content, not the content around the container.
- Test with the longest plausible string, not the shortest.
Content hierarchy per page
Every page answers one question. The hierarchy makes that question and its answer scannable.
Page title ← what is this page
Primary content ← the answer to why the user is here
Supporting content ← context that helps the primary
Actions ← what to do next
Metadata ← secondary info (dates, authors, tags)
Progressive disclosure
Don't show everything at once. Layer information by relevance:
| Layer | Show | How |
|---|---|---|
| Essential | Always | Visible on load |
| Supplementary | On demand | Expandable sections, tooltips, "Learn more" |
| Reference | On search | Help docs, FAQs, knowledge base |
Each layer deeper should serve fewer users but serve them well.
Scannability rules
- Front-load key information in every sentence, heading, and label.
- Use headings as statements, not categories. "Your bill is overdue" not "Billing".
- Break text at 2–3 sentence paragraphs for UI context.
- Lists for 3+ parallel items (but follow
canon-ux-writingfor when lists earn their place). - Bold the one phrase per paragraph that carries the meaning if a user reads nothing else.
Content inventory
Before redesigning, audit what exists:
| For each content piece | Record |
|---|---|
| What is it? | Page, modal, toast, email, error |
| Who owns it? | Product, marketing, engineering, legal |
| When was it last updated? | Date |
| Is it still accurate? | Yes / No / Partially |
| Does it serve the user's task? | Yes / No |
Delete what fails the last two questions.
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.
- 10d ago First seen · 89 lines · 68 tokens per session scan A b3289a7f6c2f
canon-content-strategy is a skill published in the GitHub repository Dragoon0x/canon (5 stars, last pushed 4mo ago), licensed MIT. It adds 68 tokens to every session and 742 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
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-compliance-accessibility-audit-v2
Accessibility Audit and Testing workflow skill. Use this skill when the user needs You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance and the operator should preserve the upstream…
accessibility-audit
Use when wCAG compliance audit — semantic HTML, ARIA, keyboard navigation, color contrast, and screen reader testing. Use when working with accessibility audit.
a11y-audit
Dedicated WCAG 2.2 AA/AAA accessibility audit across 10 dimensions (A1-A10) covering semantic HTML, keyboard navigation, ARIA patterns, color contrast, forms, images/media, responsive/zoom, motion/animation, reading/content, and legal compliance. Goes far beyond surface-level design-review checks with deep…
motion-video
Product animation, UI motion, portfolio videos — Apple-grade reveals, motion tokens, full production pipelines.