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 frontend-orchestratorgit 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/frontend-orchestrator)<a href="https://agentmods.dev/skills/sanky369/vibe-building-skills/frontend-orchestrator"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/frontend-orchestrator/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/frontend-orchestrator"><img src="https://agentmods.dev/badge/skills/sanky369/vibe-building-skills/frontend-orchestrator.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.00184 | $0.02185 |
| Opus 5 | $0.00092 | $0.01092 |
| Sonnet 5 | $0.00037 | $0.00437 |
| Haiku 4.5 | $0.00018 | $0.00218 |
Grade A, and why
frontend-orchestrator 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 13d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Design Orchestrator
You are a dispatcher, not a lecturer. Given a broad design request, inspect the codebase, diagnose its design maturity from evidence (never from a questionnaire), pick one implementation path, and hand off to concrete skills in dependency order — stating what artifact each step produces for the next. The governing principle: fix foundations before surfaces. Polishing animations on top of 50 drifted hex codes is wasted work.
When to use / when not to
- Use for broad, multi-concern, or vague requests ("make it better", "it looks amateur", "plan our design system").
- Do NOT use when the request names a single concern. Route directly:
- Spacing/type/color tokens missing or drifting →
skills/frontend-design/design-foundation - "Spacing/alignment/responsive is broken" →
skills/frontend-design/layout-system - "Fonts/text look off" →
skills/frontend-design/typography-system - "Colors clash / need dark mode" →
skills/frontend-design/color-system - "Cluttered / can't tell what's important" →
skills/frontend-design/visual-hierarchy-refactoring - Errors, loading, animation, a11y, perf → the matching skill in
skills/frontend-design/
- Spacing/type/color tokens missing or drifting →
Step 1 — Inspect the codebase (do this before asking anything)
Run these checks and record findings as evidence:
- Token infrastructure. Glob for
tailwind.config.{js,ts,cjs,mjs},**/globals.css,**/index.css,**/tokens*,**/*theme*. Read what exists. Tailwind v4 projects define tokens in CSS via@theme; v3 in the config file. - Color drift. Grep component/CSS files for
#[0-9a-fA-F]{3,8}\bandrgb\(|rgba\(|hsl\(. Count distinct values. >15 raw colors outside a token file = no working color system. - Spacing/type drift. Grep for
font-size:|text-\[|\d+px. Arbitrary Tailwind values (p-[13px],text-[15px]) and one-off px values = no scale. - Component structure. Is there a
components/(orui/) directory? Are buttons/inputs reused components or copy-pasted markup? Grep for<buttonoccurrences vs. aButtoncomponent. - Dark mode & a11y signals. Grep for
prefers-color-scheme|dark:andaria-|sr-only|prefers-reduced-motion. - Interaction signals. Grep for
transition|animation|@keyframes— none at all, ortransition: alleverywhere, both tell you something.
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.
- 13d ago First seen · 133 lines · 184 tokens per session scan A 2c54d8b23277
frontend-orchestrator is a skill published in the GitHub repository sanky369/vibe-building-skills (30 stars, last pushed 2mo ago), licensed MIT. It adds 184 tokens to every session and 2,185 once invoked, about $0.0009 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.