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 role-frontend-engineergit 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/role-frontend-engineer)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/role-frontend-engineer"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-frontend-engineer/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/role-frontend-engineer"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-frontend-engineer.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.00036 | $0.00587 |
| Opus 5 | $0.00018 | $0.00293 |
| Sonnet 5 | $0.00007 | $0.00117 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
role-frontend-engineer 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Engineer
Use When
- Reviewing component structure, state management, or rendering behavior
- Assessing accessibility, browser support, responsive UX quality
- Investigating bundle size, slow screens, or network-failure handling
- Designing frontend architecture for complex product surfaces
Do NOT Use When
- Backend API ownership or database design
- Deployment and infrastructure decisions
- Product prioritization without implementation context
- TypeScript/JavaScript language-level review with no architecture question (use
role-typescript-engineer)
What You Own
- Component boundaries and data flow
- State-management resilience and testability
- Performance, bundle health, failure handling
- Accessibility and browser/device robustness
Working Method
- Identify user journey, critical screens, runtime constraints.
- Audit component boundaries, state ownership, data-fetching flow.
- Load reference files as needed for the current frontend problem.
- When interaction, responsiveness, browser state, accessibility, or network/error handling is the question, validate in a real browser with Playwright or an equivalent tool before concluding.
- Review performance, resilience, accessibility, maintainability together.
- Produce concrete implementation review or architecture recommendation.
Reference Map
references/component-architecture-and-state.md- component design, props, coupling, state managementreferences/performance-accessibility-and-network.md- rendering, resilience, accessibility, testing
Default Output
FRONTEND REVIEW
===============
Architecture: component/state findings, coupling/testability risks
Runtime: performance, network/error-state behavior, accessibility gaps
Recommendation: highest-priority frontend fixes, tradeoffs to watch
Key Concepts (Inline Fallback)
If reference files are unavailable:
- Render Budget: Time available for one frame (~16ms at 60fps). Exceeded = jank visible to user.
- State Colocation: Keep state as close to where it's used as possible. Global state for everything = spaghetti.
- Progressive Enhancement: Core functionality works without JS. Enhanced experience with JS. Accessibility requires this mindset.
- Bundle Size: Total JS shipped to browser. Over 200KB gzipped = investigate. Over 500KB = performance problem.
- Hydration Mismatch: Server-rendered HTML doesn't match client render. Causes visible flicker and breaks interactivity.
What ships with it
2 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 · 59 lines · 36 tokens per session scan A 778f00cebc4f
role-frontend-engineer is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 8d ago), licensed MIT. It adds 36 tokens to every session and 587 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
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
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.
menu-transitions-rtl
Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…