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.
npx agentmods add skills/ne11nn/cantos-plugin/ui-refactornpx skills add ne11nn/cantos-plugin --skill ui-refactorgit clone --depth 1 https://github.com/ne11nn/cantos-pluginWrote 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/skills/ne11nn/cantos-plugin/ui-refactor)<a href="https://agentmods.dev/skills/ne11nn/cantos-plugin/ui-refactor"><img src="https://agentmods.dev/badge/skills/ne11nn/cantos-plugin/ui-refactor.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 | $0.00061 | $0.00511 |
| Opus 5 | $0.00030 | $0.00255 |
| Sonnet 5 | $0.00012 | $0.00102 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
ui-refactor 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 3d 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
UI Refactoring and Design
This skill applies tactical, logical rules to user interface design. It prioritizes clarity, hierarchy, and systems over "artistic talent."
Core Workflow
- Feature First: Do not start by designing a "shell" (nav bars, sidebars). Start with the specific functionality (e.g., the search form, the contact card).
- Low Fidelity: Ignore color, shadows, and fonts initially. Design in grayscale using a thick marker or basic wireframes to solve layout and spacing first.
- Define Systems: Do not use arbitrary values. establishing restrictive systems for spacing, type, and color immediately.
- Refine: Apply specific tactics for hierarchy, depth, and polish.
Domain-Specific Tactics
Consult these references for specific implementation rules:
- Making elements stand out/fit in: See hierarchy.md (Size, weight, contrast, semantics).
- Whitespace and alignment: See layout-spacing.md (Grids, spacing scales, density).
- Text and fonts: See typography.md (Type scales, line-height, fonts).
- Colors and palettes: See color.md (HSL, saturation, accessible contrast).
- Images, shadows, and polish: See depth-and-polish.md (Light sources, assets, finishing touches).
Quick Heuristics
- Limit Choices: If you can't decide between two options, you have too many choices. constrain your inputs (colors, font sizes, spacing) to a pre-defined scale.
- Personality:
- Serious/Elegant: Serif fonts, sharp corners, gold/blue colors, formal language.
- Playful/Friendly: Rounded sans-serifs, large border-radius, pink/orange, casual language.
- Complexity: Do not design for edge cases first. Design the "happy path" (simple version), then iterate for complexity.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 33 lines · 61 tokens per session scan A 7782f276c0d0
ui-refactor is a skill published in the GitHub repository ne11nn/cantos-plugin (1 stars, last pushed 3d ago), licensed MIT. It adds 61 tokens to every session and 511 once invoked, about $0.0003 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 skills, from other repositories
frontend-aesthetics
How to make frontends that look genuinely designed instead of generic "AI slop", and how to verify UI work the pipeline can't catch with a test suite. Load whenever a task builds or restyles a user-facing surface — a page, a component, a full redesign, a dashboard, a marketing site. Covers distinctive typography…
frontend-audit
ProductionOS frontend quality scanner. Auto-activates when editing React/Vue/Svelte components, CSS, or layout files. Checks accessibility, responsive design, performance, and design system consistency.
design-patterns
Modern design system patterns for 2025. Covers design tokens, OKLCH color systems, fluid typography, animations, dark mode, shadcn/ui components, and Figma handoff. Use when implementing UI styles, theming, accessibility, and visual polish.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
design-to-code-check
Check alignment between a specific design specification and its code implementation — a focused, single-component or single-screen comparison. Trigger when someone says: does this match the design, check implementation, design code alignment, what's different between the design and the build, spec check…