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/KaelSensei/MagicAIBuilderWrote 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/kaelsensei/magicaibuilder/beautify)<a href="https://agentmods.dev/commands/kaelsensei/magicaibuilder/beautify"><img src="https://agentmods.dev/badge/commands/kaelsensei/magicaibuilder/beautify/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/kaelsensei/magicaibuilder/beautify"><img src="https://agentmods.dev/badge/commands/kaelsensei/magicaibuilder/beautify.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.00000 | $0.01221 |
| Opus 5.5 | $0.00000 | $0.00488 |
| Sonnet 5.5 | $0.00000 | $0.00244 |
| Haiku 4.5 | $0.00000 | $0.00122 |
Grade A, and why
beautify 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beautify Command – UI Enhancement Workflow
When /beautify <component or page description> is invoked, immediately execute the following steps.
Skills used: web-performance (PageSpeed and Core Web Vitals checklist for the affected page).
Step 1: Load Project Context
- Assume the project root as the working directory
- Load and respect all Cursor rules from
.cursor/rules/*.mdc - Read core project documentation if present:
README.md- Design system or style guide documentation
- Component library documentation
- Identify the current Git branch and assume it is a feature/enhancement branch, not
main
Step 2: Understand the Target
- Parse the component or page description provided after
/beautify - Determine:
- Which component(s) or page(s) need enhancement
- Current visual state and pain points
- Desired aesthetic outcome (modern, minimal, bold, etc.)
- Locate the exact files involved (components, styles, assets)
- Analyze existing design patterns in the project before proposing changes
Step 3: Design Consistency Check (Mandatory)
Before writing any code:
- Identify the project's design system:
- Color palette (primary, secondary, accent colors)
- Typography hierarchy (fonts, sizes, weights)
- Spacing system (margins, padding, gaps)
- Component patterns (buttons, cards, inputs)
- Check for:
- Existing UI libraries (Tailwind, styled-components, etc.)
- Theme configuration files
- Design tokens or CSS variables
- Ensure enhancements respect existing design language
- If design direction is unclear, ask before proceeding
Step 4: Implement Visual Enhancements
Apply improvements following these priorities:
4.1 Layout & Spacing
- Improve visual hierarchy with consistent spacing
- Ensure proper alignment and grid structure
- Add appropriate white space for breathing room
4.2 Typography
- Enhance readability with proper font sizing
- Improve text hierarchy (headings, body, captions)
- Ensure sufficient contrast ratios (WCAG AA minimum)
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 · 170 lines · 0 tokens per session scan A 40c8ff5296f6
beautify is a command published in the GitHub repository KaelSensei/MagicAIBuilder (2 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,221 tokens. 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
review
Review code changes against project conventions.
icon-generate
You are tasked with generating a new icon for the Hogwarts icon system using AI-assisted design.
icon-add
You are tasked with adding a new icon to the Hogwarts icon system.
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.