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 Plazmodium/odin-workflow --skill frontend-ui-engineeringgit clone --depth 1 https://github.com/Plazmodium/odin-workflowWrote 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/plazmodium/odin-workflow/frontend-ui-engineering)<a href="https://agentmods.dev/skills/plazmodium/odin-workflow/frontend-ui-engineering"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/frontend-ui-engineering/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/plazmodium/odin-workflow/frontend-ui-engineering"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/frontend-ui-engineering.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.00023 | $0.00307 |
| Opus 5.5 | $0.00009 | $0.00123 |
| Sonnet 5.5 | $0.00005 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
frontend-ui-engineering 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.
What it actually says
frontend-ui-engineering
When To Use
- Creating or changing visible UI.
- Modifying component structure, state, forms, navigation, or styling.
- Fixing user-facing browser behavior.
Workflow
- Inspect existing design system, component patterns, routes, and state conventions.
- Define desktop, mobile, loading, empty, error, and disabled states.
- Preserve established visual language unless asked to redesign.
- Implement semantic markup and keyboard-accessible interactions.
- Validate responsive behavior at relevant breakpoints.
- Check console, network, and visible behavior when feasible.
- Add or update tests for meaningful behavior.
Anti-Rationalization
| Excuse | Rebuttal |
|---|---|
| "It compiles, so the UI is done." | UI must work in the browser and across states. |
| "Accessibility can come later." | Accessibility is part of correctness for UI. |
| "The screenshot looks fine." | Static appearance does not prove interactions, errors, or mobile layout. |
Verification
- UI handles core states and relevant viewport sizes.
- Interactions work with keyboard and pointer where applicable.
- Runtime evidence or tests support the result.
Exit Criteria
- The UI is usable, accessible, responsive, and consistent with local conventions.
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 · 43 lines · 23 tokens per session scan A 09b8c40aa7f0
frontend-ui-engineering is a skill published in the GitHub repository Plazmodium/odin-workflow (0 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 307 once invoked, about $0.0001 per session on Opus 5.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-09-01.
Other skills, from other repositories
b123d-modeling
Use this skill when asked to model, build, or modify a 3D part or assembly with build123d — from a text description, a technical drawing (image or PDF), dimensions in a spec, or an existing STEP/STL file.
wireframe-power-bi-page
Use when planning the layout of a Power BI report page. Triggers on phrases like "wireframe a page", "layout for a dashboard", "where should I put the visuals", "design the page layout", "how should I arrange these visuals". Covers canvas geometry (1280x720), 5 validated layouts, the pbirlayoutgrid tool, spacing math.
design-power-bi-report
Use when polishing or theming a Power BI report — typography, colors, KPI cards, slicer placement, formatting taste decisions. Triggers on phrases like "make my report look better", "improve the design", "what colors should I use", "format this dashboard", "report doesn't look professional".
openclaw-color-palette
Design-grade color processing suite — generate harmonious palettes from any seed color, check WCAG 2.1 AA/AAA contrast accessibility, convert between hex/RGB/HSL/HSV/CMYK, simulate 8 color blindness types, and extract dominant colors from images. Use when: (1) user says 'generate a color palette' or 'give me a color…
motion-interaction
Add purposeful interaction and motion to HTML designs, including state transitions, feedback, navigation, disclosure, and reduced-motion behavior.
conversational-ux
Design voice and conversational interfaces — dialog flows, error recovery, and persona. Use when the interface speaks and listens rather than being tapped. For graphical input collection, use form-design.