Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/trabian/fluxwing-skillsnpx agentmods add skills/trabian/fluxwing-skills/fluxwing-screen-scaffolderWrote 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/trabian/fluxwing-skills/fluxwing-screen-scaffolder)<a href="https://agentmods.dev/skills/trabian/fluxwing-skills/fluxwing-screen-scaffolder"><img src="https://agentmods.dev/badge/skills/trabian/fluxwing-skills/fluxwing-screen-scaffolder/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/trabian/fluxwing-skills/fluxwing-screen-scaffolder"><img src="https://agentmods.dev/badge/skills/trabian/fluxwing-skills/fluxwing-screen-scaffolder.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.00055 | $0.07689 |
| Opus 5 | $0.00028 | $0.03845 |
| Sonnet 5 | $0.00011 | $0.01538 |
| Haiku 4.5 | $0.00006 | $0.00769 |
Grade A, and why
Fluxwing Screen Scaffolder 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 — 883 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fluxwing Screen Scaffolder
Create complete screen designs using the uxscii standard by orchestrating specialized agents.
Data Location Rules
READ from (bundled templates - reference only):
{SKILL_ROOT}/../uxscii-component-creator/templates/- 11 component templates{SKILL_ROOT}/templates/- 2 screen examples{SKILL_ROOT}/docs/- Documentation
INVENTORY sources (check all for available components):
./fluxwing/components/- User-created components (FIRST PRIORITY)./fluxwing/library/- Customized template copies{SKILL_ROOT}/../uxscii-component-creator/templates/- Bundled templates (READ-ONLY)
WRITE to (project workspace):
./fluxwing/screens/- Your created screens (via composer agent)
NEVER write to skill directories - they are read-only!
LOAD for copy-on-update logic:
{SKILL_ROOT}/../shared/docs/copy-versioning.md- Versioning pattern for existing screens
Your Task
⚠️ YOU ARE AN ORCHESTRATOR - DO NOT DO THE WORK YOURSELF! ⚠️
Your role is to spawn agents using the Task tool. You coordinate agents, you don't create components directly.
Help the user scaffold a complete screen by orchestrating agents in two phases:
- Phase 1 (Parallel): Spawn multiple designer agents - one per missing component using multiple Task tool calls in ONE message
- Phase 2 (Sequential): After all components exist, spawn composer agent
Concurrency Model:
- If 6 components are missing → spawn 6 agents in parallel using 6 Task tool calls in ONE message (~6x faster)
- Then wait for all to complete before composing screen
CRITICAL: Use the Task tool to spawn agents. Do NOT use TodoWrite and work through tasks yourself. Do NOT create files yourself.
MULTI-SCREEN SCENARIOS:
If user requests N screens (N > 1):
- ⚠️ DO NOT create TodoWrite list with N screen tasks and work through them
- ⚠️ DO NOT use Write/Edit tools to create screen files yourself
- ⚠️ DO NOT "help" composer agents by pre-creating any files
- ✅ DO spawn N composer agents in parallel (one per screen)
- ✅ DO send ONE message with ALL Task calls (parallel execution)
- ✅ DO let each composer agent independently create all 3 files (.uxm, .md, .rendered.md)
What ships with it
7 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.
- 12d ago First seen · 883 lines · 55 tokens per session scan A 33e3b70202f1
Fluxwing Screen Scaffolder is a skill published in the GitHub repository trabian/fluxwing-skills (18 stars, last pushed 9mo ago), licensed MIT. It adds 55 tokens to every session and 7,689 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-30.
Other skills, from other repositories
accessibility
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
information-architecture
Design the structure of a website or product including sitemap, navigation, URL structure, content types, taxonomy, and labeling. Use this skill whenever the user asks to plan a sitemap, design navigation, structure URLs, define content types, build taxonomies, design site search, or organize content at the system…
frontend
Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.
shiny-bslib-theming
Advanced theming for Shiny apps using bslib and Bootstrap 5. Use when customizing app appearance with bstheme(), Bootswatch themes, custom colors, typography, brand.yml integration, Bootstrap Sass variables, custom Sass/CSS rules, dark mode and color modes, dynamic theme switching, real-time theming, theme inspection…
tastemaker
Generate genuinely beautiful, on-brand UI instead of generic "AI slop" — use whenever the user asks to build, design, style, or improve a UI, landing page, dashboard, app screen, or component, whenever a PRD/spec needs a design pass before implementation, whenever the user pastes reference images/Pinterest/Dribbble…
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…