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/optimize)<a href="https://agentmods.dev/commands/dragoon0x/canon/optimize"><img src="https://agentmods.dev/badge/commands/dragoon0x/canon/optimize/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/optimize"><img src="https://agentmods.dev/badge/commands/dragoon0x/canon/optimize.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.00022 | $0.00523 |
| Opus 5.5 | $0.00009 | $0.00209 |
| Sonnet 5.5 | $0.00004 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00052 |
Grade A, and why
optimize 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.
What it actually says
/optimize
Measure, then cut. Not vibes-based "it feels slow" — concrete targets from canon-performance.
Targets (Core Web Vitals, "Good" thresholds)
- LCP: ≤ 2.5s
- INP: ≤ 200ms
- CLS: ≤ 0.1
- TTFB: ≤ 800ms
Budgets
- Initial JS (parsed+compiled): ≤ 200KB gzipped for most apps, ≤ 350KB for complex.
- CSS: ≤ 60KB gzipped.
- Hero/LCP image: ≤ 200KB, served at correct dimensions,
fetchpriority="high", no lazy. - Total page weight (first load): ≤ 1.5MB.
Checklist
- LCP image: identified, preloaded,
fetchpriority="high", notloading="lazy", served at rendered size. - Fonts:
font-display: swap, 1–2 families max, subset if possible, preload the critical weight. - CLS: width and height attributes on every
<img>, reserved space for ads and embeds, no layout-shifting web fonts without proper fallbacks. - JS: code-split by route, lazy-load below-the-fold interactive components, tree-shake dead imports, replace heavy libs (moment → date-fns, lodash-full → per-function).
- Third parties: audit. Every third-party script pays rent or leaves.
- Images: modern formats (AVIF with WebP fallback),
srcsetfor responsive, no raw PNG/JPG where a vector works. - Caching: long cache for hashed assets, short/no cache for HTML, service worker only if you own the consequences.
- INP: keep long tasks ≤ 50ms, debounce input handlers, defer non-critical work with
requestIdleCallbackorscheduler.postTask.
Output
- Current vs target table for each metric.
- Top 5 interventions ranked by impact.
- Before/after bundle report if applicable.
- Specific code changes, not "consider optimizing".
Success criteria
Hits all four CWV "Good" thresholds on a median mobile device over 4G. Bundle under budget. No single task over 50ms on the critical path.
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 · 45 lines · 22 tokens per session scan A 4b229f2830a5
optimize is a command published in the GitHub repository Dragoon0x/canon (6 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 523 once invoked, about $0.0001 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
speckit.git.remote
Detect Git remote URL for GitHub integration.
speckit.myext.myextcmd
Override of the myext extension's myextcmd command.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.