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/Muminur/frontend-design-craft-skillWrote 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/muminur/frontend-design-craft-skill/arrange)<a href="https://agentmods.dev/commands/muminur/frontend-design-craft-skill/arrange"><img src="https://agentmods.dev/badge/commands/muminur/frontend-design-craft-skill/arrange.svg" alt="Measured on agentmods" 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.00011 | $0.00549 |
| Opus 5 | $0.00005 | $0.00275 |
| Sonnet 5 | $0.00002 | $0.00110 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
arrange 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 7d 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
/arrange
Diagnose and fix layout problems specifically. Do not touch type, color, or motion.
Target
$ARGUMENTS
Procedure
- Spacing audit. List every spacing value used. If any are off the 4px scale (
4, 8, 12, 16, 20, 24, 32, 40, 48, 64, 80, 96), flag them and replace unless there is an explicit optical-alignment reason. - Proximity check. For each grouped element (card, list item, form field), verify that internal spacing is tighter than external spacing. Failure: card padding 24px and internal gap 24px (no visual grouping). Fix: padding 24px, internal gap 8–12px.
- Vertical rhythm. Pick section, subsection, and within-section spacing values and apply consistently:
- Section break: 96–160px (brand) / 48–80px (product)
- Subsection: 48–64px / 32–40px
- Within section: 24–32px / 16–24px
- Grid check. Is there a stated grid (12-col, 6-col, custom)? Are elements aligning to it? If layout feels random, define and apply a grid.
- Hero check. If the page has a hero, is it the lazy centered-stack-with-image-below pattern? If so, propose an asymmetric layout option (e.g., 7/5 split, headline left + product image right).
- Responsive check. Do layouts change between breakpoints, or just resize? A 3-column desktop grid should not become a stretched 1-column grid on mobile — it should restructure (vertical stack, horizontal scroll, or different component entirely).
- Alignment check. Look for optical mis-alignments (icon next to label, button text, heading-to-body baselines).
Output
## Arrange complete
**Spacing scale enforced:** [scale]
**Vertical rhythm:** [section/subsection/within values]
**Grid:** [columns / gutter]
**Issues fixed:**
- [list]
**Layout changes:**
- [list of structural changes — e.g., "hero restructured to 7/5 asymmetric"]
If a hero restructure is proposed, show the user the before/after structure (in words or ASCII) before implementing.
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.
- 7d ago First seen · 44 lines · 11 tokens per session scan A 3c005787c757
arrange is a command published in the GitHub repository Muminur/frontend-design-craft-skill (4 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 549 once invoked, about $0.0001 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 commands, from other repositories
ux-recommend
The v2 flagship. Runs the 5-parallel-search Python engine across 11 data manifests (75+ styles, 170+ palettes, 65+ type pairs, 120+ components, 170+ industries, 110+ UX laws, 50+ motion presets, 120+ anti-patterns, 92 brand specs) and returns a complete recommended design system for your project — with always-on…
color-specialist
Use when colour is failing. Contrast below AA, a palette with no system behind it, dark mode that is only inverted light mode, or semantic colours that carry no meaning.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
wcag-audit
Accessibility audit based on WCAG 2.1/2.2 and the axe-core reference.
revisar-ui
Auditoria visual retroativa de 6 pilares do código frontend implementado.
/a11y-audit
Auditoría de accesibilidad WCAG 2.2 completa con escaneo de HTML/componentes. Detecta: alt text faltante, problemas de contraste, navegación por teclado, etiquetas ARIA, gestión de focus, jerarquía de encabezados, etiquetas de formularios. Genera reporte accionable con instrucciones de remediación.