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 skills add sanky369/vibe-building-skills --skill visual-hierarchy-refactoringgit clone --depth 1 https://github.com/sanky369/vibe-building-skillsWrote 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/sanky369/vibe-building-skills/visual-hierarchy-refactoring)<a href="https://agentmods.dev/skills/sanky369/vibe-building-skills/visual-hierarchy-refactoring"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/visual-hierarchy-refactoring/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/skills/sanky369/vibe-building-skills/visual-hierarchy-refactoring"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/visual-hierarchy-refactoring.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.00149 | $0.01926 |
| Opus 5 | $0.00075 | $0.00963 |
| Sonnet 5 | $0.00030 | $0.00385 |
| Haiku 4.5 | $0.00015 | $0.00193 |
Grade A, and why
visual-hierarchy-refactoring 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 12d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Hierarchy Refactoring
Take a real screen or component and refactor it so the eye lands on the right things in the right order. The deliverable is refactored code plus a before/after hierarchy audit — not design commentary. Governing principles: hierarchy is a function of size, weight, and lightness contrast — color is the last resort, and the fastest fix is de-emphasis: quiet the noise before amplifying the signal.
When to use / handoffs
- Use when a specific screen is cluttered, flat, unscannable, or "looks off" despite sane tokens.
- No consistent tokens exist at all (every fix would be a new magic number) →
skills/frontend-design/design-foundationfirst. - The problem is structural (columns misaligned, breaks on mobile) →
skills/frontend-design/layout-system. - Font sizes themselves are chaotic across the app →
skills/frontend-design/typography-system. - Palette is the problem (clashing hues, contrast failures everywhere) →
skills/frontend-design/color-system.
Step 1 — Inspect the target
- Get the actual component. Read the file(s) for the screen the user named; if none named, ask for the one screen that matters most (this is the only intake question that blocks). Render or screenshot it if the environment allows.
- Read the available tokens (spacing scale, text sizes, grey ramp) — every fix must use them.
- Detect hierarchy smells in the code, with counts:
- Emphasis inflation: how many elements per screen are bold, colored, large, or bordered? (>3 competing emphases = nothing is emphasized)
- Cramped spacing: padding/margins ≤8px between unrelated groups
- True greys / pure black:
#808080-family,#000,text-gray-500on colored surfaces - Uniform sizing: title, body, and metadata within a step of each other
- Even spacing everywhere: identical gap inside and between groups (kills Gestalt grouping)
- Border overuse: boxes-in-boxes where spacing would separate
Step 2 — Build the hierarchy audit
What ships with it
1 file 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.
- 12d ago First seen · 108 lines · 149 tokens per session scan A 8105a7d1f2b8
visual-hierarchy-refactoring is a skill published in the GitHub repository sanky369/vibe-building-skills (30 stars, last pushed 2mo ago), licensed MIT. It adds 149 tokens to every session and 1,926 once invoked, about $0.0007 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-30.
Other skills, from other repositories
avalonia-layout-zafiro
Guidelines for modern Avalonia UI layout using Zafiro.Avalonia, emphasizing shared styles, generic components, and avoiding XAML redundancy.
core-components
Core component library and design system patterns. Use when building UI, using design tokens, or working with the component library.
ui-web
Web UI - glassmorphism, Tailwind, dark mode, accessibility.
app-ui-design
Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.
mulmoterminal-theme
Build a colour scheme of your own for MulmoTerminal — one that joins Midnight, Nord, Daylight and Solarized in Settings' theme picker and can then be pinned per project. Writes themes in /.mulmoterminal/config.json, the whole-app palette (panels, borders, accent, text), which has no UI for creating one — Settings only…
frontend-design
A design guide for building polished web interfaces such as pages, dashboards, forms, navigation, and reusable UI components. It covers HTML, CSS, JavaScript, and common frontend frameworks.