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.5 | $0.00014 | $0.00235 |
| Sonnet 5.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 2mo 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.
- 2mo 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 2mo ago), licensed MIT. It adds 36 tokens to every session and 587 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-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…