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 saemihemma/lead-producer-oss --skill team-frontend-teamgit clone --depth 1 https://github.com/saemihemma/lead-producer-ossWrote 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/saemihemma/lead-producer-oss/team-frontend-team)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/team-frontend-team"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/team-frontend-team/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/saemihemma/lead-producer-oss/team-frontend-team"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/team-frontend-team.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.00035 | $0.00507 |
| Opus 5 | $0.00017 | $0.00253 |
| Sonnet 5 | $0.00007 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
team-frontend-team 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 11d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Team
Purpose
Decide whether an interface is usable, implementable, accessible, and technically healthy to ship.
Composition
- role-ui-ux-designer: flow quality, hierarchy, clarity, accessibility
- role-frontend-engineer: implementation quality, runtime behavior, state health
- role-backend-engineer: API and contract advisor for integration risk
- Synthesis: trade-offs, acceptance
Use When
- Reviewing UI feature, screen, or frontend-heavy flow
- Checking accessibility, responsiveness, client-side architecture
- Evaluating frontend-backend integration quality
Do NOT Use When
- Backend-only, infrastructure-only, or product-only
- Brand-definition with no implementation or UX question
- Narrow shadcn/ui method (use
workflow-shadcn-ui)
Workflow
- Define critical user journey, key screens/states, and existing design patterns worth reusing.
- Review UX, frontend implementation, and API dependence together.
- When interaction, responsiveness, accessibility, browser state, or network/error behavior is in question, validate in a real browser with Playwright or an equivalent tool before trusting code-only review.
- Performance, failure handling, accessibility, and AI slop risk are part of the same verdict.
- Synthesize trade-offs into one frontend recommendation.
Default Output
FRONTEND TEAM REVIEW
====================
Journey: main user flow, friction points, existing design leverage
Implementation: state/rendering/integration risks
Quality: accessibility gaps, responsive/failure-state issues, AI slop risk
Recommendation: ship / revise / escalate, highest-priority fixes
Conflict Resolution
- UI/UX Designer owns user-experience quality. Frontend Engineer owns implementation feasibility.
- When UX and implementation conflict, find the smallest UX change that resolves the technical constraint.
Anti-Drift Rules
- Do not expand into backend redesign under frontend review label.
- Reuse proven design leverage before inventing new UI language.
- Call out AI slop risk explicitly when it appears.
- Accessibility and error states are shipping requirements, not nice-to-haves.
- Prefer real-browser evidence over code-only guesses when UI behavior is the question.
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.
- 11d ago First seen · 54 lines · 35 tokens per session scan A 7d966f970dd4
team-frontend-team is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 7d ago), licensed MIT. It adds 35 tokens to every session and 507 once invoked, about $0.0002 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-31.
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…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…