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 lfyxhappy/lfcode --skill ui-implementergit clone --depth 1 https://github.com/lfyxhappy/lfcodeWrote 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/lfyxhappy/lfcode/ui-implementer)<a href="https://agentmods.dev/skills/lfyxhappy/lfcode/ui-implementer"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/ui-implementer.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.1 | $0.00060 | $0.00344 |
| Opus 5 | $0.00030 | $0.00172 |
| Sonnet 5 | $0.00012 | $0.00069 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
ui-implementer 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 Implementer
Turn a concrete interface requirement into maintainable, tested UI behavior.
Workflow
- Read applicable instructions and inspect the target route, components, state flow, design tokens, assets, existing tests, and current worktree changes.
- Establish the real startup or packaging path and reproduce the current state at relevant viewport sizes before editing.
- Translate the requirement into states and interactions including loading, empty, error, disabled, keyboard, narrow, and long-content cases.
- Reuse existing primitives and styles. Make the smallest scoped implementation and keep data, behavior, and presentation boundaries clear.
- Run focused unit or component checks, then build and exercise the real page when the change is UI-visible. Inspect DOM, screenshots, console errors, page errors, and failed requests.
- Check responsive layout, focus order, semantics, contrast, overflow, and persistence where applicable. Report unverified visual or platform states.
Boundaries
- Do not replace unrelated design systems, add placeholder behavior, or hide errors just to match a screenshot.
- Do not claim a source build updated the installed application; verify the actual served or packaged artifact when required.
- Avoid external assets and network calls unless explicitly requested and authorized.
Completion check
Report changed components, states exercised, build and runtime evidence, screenshots or DOM checks, and remaining browser or platform limitations.
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 · 28 lines · 60 tokens per session scan A 28a62f536863
ui-implementer is a skill published in the GitHub repository lfyxhappy/lfcode (2 stars, last pushed 5d ago), licensed MIT. It adds 60 tokens to every session and 344 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-09-05.
Other skills, from other repositories
Mandu UI
UI component library integration and accessibility patterns.
uicraft
Create, improve, audit, and polish distinctive production-grade web interfaces, including marketing/landing pages and personal portfolio sites. Use for UI or frontend design, responsive layouts, typography, color, motion, UX copy, accessibility, performance, design-system alignment, onboarding, edge cases, or visual…
figma
Complete guide for the Figma plugin — REST API access, real-time selection monitoring via CDP, and the figma-app interactive UI. Read this IMMEDIATELY when the user asks to work with Figma.
design-handoff
Use when a design is ready for engineering — produce an implementation-ready spec covering layout, tokens, states, responsive behavior, edge cases, motion, and accessibility.
design-system-architecture
A guide for turning a brand’s visual rules into a reusable design system. Design tokens are shared values such as colours, spacing, and font sizes; components are reusable interface building blocks.
design-taste-frontend
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.