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/educlopez/ui-craftWrote 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/educlopez/ui-craft/bolder)<a href="https://agentmods.dev/commands/educlopez/ui-craft/bolder"><img src="https://agentmods.dev/badge/commands/educlopez/ui-craft/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/educlopez/ui-craft/bolder"><img src="https://agentmods.dev/badge/commands/educlopez/ui-craft/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.00064 | $0.00453 |
| Opus 5.5 | $0.00026 | $0.00181 |
| Sonnet 5.5 | $0.00013 | $0.00091 |
| Haiku 4.5 | $0.00006 | $0.00045 |
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
Make the UI at $ARGUMENTS bolder. Load the ui-craft skill and read references/craft-intent.md.
This is amplitude, not decoration. Increase editorial confidence while staying anti-slop clean.
Apply in order (edit code directly):
- Declare an updated Craft Read — one line: what changed (variance, motion, signature).
- Raise DESIGN_VARIANCE by +1–2 (cap 10). Product surfaces: asymmetric offset, stronger metric hierarchy, or display moment in shell. Marketing: stronger hero composition, section rhythm break, or typographic scale — per
references/craft-intent.mdvariance table. - Raise MOTION_INTENSITY by +1 (cap 10) if below 8 — add one purposeful entrance or hover choreography on the focal element only. Honor
prefers-reduced-motion. - Typography — increase display weight or size one step; tighten tracking on headlines; ensure numbers stay
tabular-nums. - Accent — strengthen focal accent placement (within 3–5 viewport budget); tint primary card or CTA — never add a second accent hue.
- Signature — add or strengthen the one signature bet if missing or weak (see craft-intent §3).
Never add: purple-cyan gradients, bounce easing, glassmorphism stacks, emoji, ALL CAPS headings, three equal icon-card grids, confetti.
Knob gating: if already at variance ≥9 or MOTION ≥9, strengthen signature and typography instead of pushing further.
Output: edit code. Print Review Format table. End with the updated Craft Read line.
Next step: /critique — confirm the added personality did not cost hierarchy or become slop (rung 1).
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 · 26 lines · 64 tokens per session scan A e08f6ce1610b
bolder is a command published in the GitHub repository educlopez/ui-craft (390 stars, last pushed 5d ago), licensed MIT. It adds 64 tokens to every session and 453 once invoked, about $0.0003 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-30.
Other commands, from other repositories
style
Apply styling to a component using the project's design system and styling approach.
summary
Generate a consolidated project brief from design artifacts. For the full spec package with YAML specs and validation, use /compile instead.
start-design-plan
Start collaborative design process with brainstorming and planning.
new-feature
Start a complete feature development process from problem framing to DOD and wireframe.
design-research
Research existing design patterns, component inventory, and open UX decisions before starting a new feature design.
checklist
Generate a custom checklist for the current feature based on user requirements.