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 julianromli/droid-factory-template --skill frontend-ui-integrationgit clone --depth 1 https://github.com/julianromli/droid-factory-templateWrote 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/julianromli/droid-factory-template/frontend-ui-integration)<a href="https://agentmods.dev/skills/julianromli/droid-factory-template/frontend-ui-integration"><img src="https://agentmods.dev/badge/skills/julianromli/droid-factory-template/frontend-ui-integration/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/julianromli/droid-factory-template/frontend-ui-integration"><img src="https://agentmods.dev/badge/skills/julianromli/droid-factory-template/frontend-ui-integration.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.00057 | $0.00726 |
| Opus 5 | $0.00028 | $0.00363 |
| Sonnet 5 | $0.00011 | $0.00145 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
frontend-ui-integration 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 9d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Frontend UI integration
Purpose
Implement or extend a user-facing workflow in our primary web application, integrating with existing backend APIs and following our design system, routing, and testing conventions.
When to use this skill
- The feature is primarily a UI/UX change backed by one or more existing APIs.
- The backend contracts, auth model, and core business rules already exist.
- The change affects only the web frontend (no schema or service ownership changes).
Inputs
- Feature description: short narrative of the user flow and outcomes.
- Relevant APIs: endpoints, request/response types, and links to source definitions.
- Target routes/components: paths, component names, or feature modules.
- Design references: Figma links or existing screens to mirror.
- Guardrails: performance limits, accessibility requirements, and any security constraints.
Out of scope
- Creating new backend services or changing persistent data models.
- Modifying authentication/authorization flows.
- Introducing new frontend frameworks or design systems.
Conventions
- Framework: React with TypeScript.
- Routing: use the existing router and route layout patterns.
- Styling: use the in-house design system components (Buttons, Inputs, Modals, Toasts, etc.).
- State management: prefer the existing state libraries (e.g., React Query, Redux, Zustand) and follow established patterns.
Required behavior
- Implement the UI changes with strong typing for all props and API responses.
- Handle loading, empty, error, and success states using existing primitives.
- Ensure the UI is keyboard accessible and screen-reader friendly.
- Respect feature flags and rollout mechanisms where applicable.
Required artifacts
- Updated components and hooks in the appropriate feature module.
- Unit tests for core presentation logic.
- Integration or component tests for the new flow (e.g., React Testing Library, Cypress, Playwright) where the repo already uses them.
- Minimal CHANGELOG or PR description text summarizing the behavior change (to be placed in the PR, not this file).
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.
- 9d ago First seen · 78 lines · 57 tokens per session scan A 37238da71ff3
frontend-ui-integration is a skill published in the GitHub repository julianromli/droid-factory-template (53 stars, last pushed 9mo ago), licensed MIT. It adds 57 tokens to every session and 726 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
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
cobejs
Use when adding a lightweight interactive globe with cobe (canvas setup, markers, interaction, performance, integration with React/Next.js).
stitch::react-components
Converts Stitch designs into modular Vite and React components, or syncs/updates existing React components to align with the latest Stitch designs, using system-level networking and AST-based validation.
seed-design
An integration guide for SEED Design, covering shared component specifications and foundations plus React and Lynx implementation guidance.
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.