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/bolder)<a href="https://agentmods.dev/commands/dragoon0x/canon/bolder"><img src="https://agentmods.dev/badge/commands/dragoon0x/canon/bolder/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/bolder"><img src="https://agentmods.dev/badge/commands/dragoon0x/canon/bolder.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.00017 | $0.00415 |
| Opus 5.5 | $0.00007 | $0.00166 |
| Sonnet 5.5 | $0.00003 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
bolder 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
/bolder
Some interfaces are too quiet. They look unfinished, not refined. This command adds presence.
What this does
- Audit the current state. Is it truly timid, or is it quiet-done-well? Don't fix what isn't broken.
- Signs an interface is too timid:
- Every text color is the same near-black gray.
- All buttons look secondary.
- Headings barely distinguish from body.
- Brand color appears once, apologetically.
- Everything is 50% opacity.
- Apply the escalation ladder:
- Type scale: push the display sizes up. H1 goes from 32 to 48+. Weight on display elements moves from 600 to 700–800.
- Hierarchy gap: widen the contrast between heading and body. Different size, different weight, different color if warranted.
- Primary action: one primary button per screen, and it looks unmistakably primary. Filled, brand color, confident.
- Brand color: use it on primary actions, on focus rings, on one signature element. Not on every border.
- Negative space: sometimes bolder means more whitespace, not more ink. A huge quiet area around a single confident element is bolder than ten loud elements.
- Hold the line on CANON discipline:
- Still WCAG AA.
- Still 4/8 grid.
- Still semantic tokens.
- No skeuomorphic shadows, no neon glows, no 3D text effects.
Output
- Before/after side by side.
- Changes grouped: type, color, space, hierarchy.
- Rationale per change in one sentence.
Success criteria
The interface has a point of view. You can identify the primary action from 6 feet away. Headings feel like headings. The brand color earns its presence.
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 · 40 lines · 17 tokens per session scan A e34a8929ccf2
bolder is a command published in the GitHub repository Dragoon0x/canon (6 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 415 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.