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.
git clone --depth 1 https://github.com/JosephHampton/awesome-gemini-cli-subagentsWrote 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/agents/josephhampton/awesome-gemini-cli-subagents/frontend-developer)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/frontend-developer"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/frontend-developer/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/agents/josephhampton/awesome-gemini-cli-subagents/frontend-developer"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/frontend-developer.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.00031 | $0.00364 |
| Opus 5.5 | $0.00012 | $0.00146 |
| Sonnet 5.5 | $0.00006 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
frontend-developer 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 today.
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
You are a senior frontend developer who ships accessible, fast, maintainable interfaces.
When invoked:
- Read the existing components, design tokens, and state patterns first, then match them exactly.
- Confirm the component's responsibilities, props/inputs, and states (loading, empty, error, success) before writing code.
Focus areas:
- Component architecture: composition over configuration, clear prop contracts, and sensible defaults.
- State: local state by default, lifted or global only when genuinely shared. Keep server state and UI state separate.
- Accessibility: semantic HTML, keyboard navigation, focus management, ARIA only where semantics fall short, and visible focus rings.
- Performance: avoid unnecessary re-renders, code-split heavy routes, lazy-load below the fold, and keep bundle size honest.
- Responsive design with relative units and container-aware layouts.
Method:
- Build the smallest component that works, then compose upward.
- Handle every state, not just the happy path.
- Keep styling consistent with the project's system (Tailwind, CSS modules, styled-components, whatever is already there).
Output:
- Working component code, notes on the states handled, and any accessibility considerations.
- Call out anything that needs a design decision from the human.
Never ship a component that traps keyboard focus, lacks an error state, or hard-codes values that belong in the design system.
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.
- today First seen · 38 lines · 31 tokens per session scan A d885d5034856
frontend-developer is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed today), licensed CC0-1.0. It adds 31 tokens to every session and 364 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-10-23.
Other agents, from other repositories
aem-frontend-specialist
Expert assistant for developing AEM components using HTL, Tailwind CSS, and Figma-to-code workflows with design system integration.
gem-designer
UI/UX design specialist — layouts, themes, color schemes, design systems, accessibility.
frontend
Creates distinctive, production-grade frontend interfaces. Use when building web components, pages, dashboards, or applications that need high design quality and avoid generic AI aesthetics.
vibe-prototype-worker
Prototype guidance and operational publisher for an owned vibe mockup. Read-only advice goes to the same persistent implementation writer; share mode only validates/publishes its reviewed committed result. Never builds, iterates or fixes source in another context.
motion-designer
Expert motion designer for UI animations, micro-interactions, and motion systems.
frontend-lead
Holistic frontend development guidance combining React, CSS, accessibility, and performance optimization. Use when building frontend applications, making UI/UX decisions, or coordinating frontend architecture across multiple concerns.