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/quieter)<a href="https://agentmods.dev/commands/dragoon0x/canon/quieter"><img src="https://agentmods.dev/badge/commands/dragoon0x/canon/quieter/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/quieter"><img src="https://agentmods.dev/badge/commands/dragoon0x/canon/quieter.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.00016 | $0.00382 |
| Opus 5.5 | $0.00006 | $0.00153 |
| Sonnet 5.5 | $0.00003 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
quieter 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
/quieter
The opposite of "make it pop." Reduce until only necessary elements remain.
What this does
- Pull the interface apart. Identify every visual element: borders, shadows, gradients, patterns, icons, emoji, dividers, background colors.
- For each, ask: does removing this harm comprehension?
- Apply the reduction order (aggressive first):
- Remove redundant icons when text is clear.
- Remove borders when whitespace alone separates.
- Remove shadows on secondary elements.
- Flatten gradients to solid colors.
- Collapse background tints that don't earn their contrast.
- Drop emoji from UI copy.
- Thin dividers (1px → hairline, or replace with spacing).
- Tighten the hierarchy:
- Fewer font weights. Aim for 2.
- Fewer font sizes. Aim for 4–5.
- Fewer colors in the UI layer. Text, background, border, accent. That's often enough.
- Trust whitespace.
canon-depthsays prefer whitespace > border > shadow in that order. - Replace visual separators with structural ones (headings, spacing) where the structure carries the meaning.
Output
- Before/after comparison.
- Count reduction: X borders removed, Y shadows flattened, Z colors consolidated.
- Whitespace increases shown as spacing tokens applied.
Anti-patterns to catch
- Drop-shadow on every card.
- Gradient backgrounds behind text.
- 1px dividers at 10% opacity doing nothing visible.
- Emoji as the only signal for a status.
- Five weights of the same font on one page.
Success criteria
The interface looks more expensive, not less. Attention flows to what matters. Nothing shouts.
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 · 46 lines · 16 tokens per session scan A f9f6b9965c1f
quieter is a command published in the GitHub repository Dragoon0x/canon (6 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 382 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
agentation-fix
Session-2 fix loop for Agentation — read structured annotations from the dev overlay and apply targeted UI fixes.
scan-ai-tells
Scan UI or marketing copy for AI-default tells and content-authenticity misses — deletion list, not a redesign brief.
ccc-theme
List, preview or switch the Commander terminal color theme (Claude, OLED Black, Matrix, or a random palette) used by hooks and terminal art. Use when the user asks to change the theme, colors or skin.
extract-foundations-from-screens
Extract canonical foundations docs (color, typography, spacing, radii) from a batch of existing SCREENSPECs. Re-runs only add new tokens and route conflicts to a Review queue. Use when SCREENSPECs already document raw values and need converging into role tokens. Do not use when foundations are already curated and…
screen-spec
Generate a screen specification from a Figma frame using MCP tools (getdesigncontext, getscreenshot), matching the SCREENSPEC.md template (layout, states). Use when documenting a specific screen. Do not use when the screen has no Figma frame or the spec already exists, for 6 or more screens (use screen-spec-fleet), or…
design-critic
Use when you want an honest read on a design instead of encouragement. What is wrong, ranked by severity, with the reason attached. Works on a screenshot, a mockup, or a described screen.