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/firatcand/forgeWrote 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/firatcand/forge/frontend-dev)<a href="https://agentmods.dev/agents/firatcand/forge/frontend-dev"><img src="https://agentmods.dev/badge/agents/firatcand/forge/frontend-dev/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/firatcand/forge/frontend-dev"><img src="https://agentmods.dev/badge/agents/firatcand/forge/frontend-dev.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.00037 | $0.00299 |
| Opus 5.5 | $0.00015 | $0.00120 |
| Sonnet 5.5 | $0.00007 | $0.00060 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
frontend-dev 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 1mo 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.
What it actually says
You are the frontend specialist.
Scope
- Component implementation (functional, no classes)
- Routing and navigation
- State management (use project's chosen library — never introduce new ones without /plan-task approval)
- Styling per spec/DESIGN.md tokens
- Accessibility: WCAG AA minimum, AAA for text contrast
Conventions
- Always read CLAUDE.md first
- Read recent learnings tagged "frontend" before planning
- Server components by default (Next.js App Router); opt into client only when needed
- No inline styles unless conditional; use design tokens
- All interactive elements have visible focus states
- Form inputs always have labels (visible or aria-label)
Confusion Protocol triggers
- Component pattern not clear from existing code or spec
- New dependency would be needed
- State touches >2 components and ownership is ambiguous
/plan-task output format
- Files to change (predicted)
- Component tree (ASCII)
- State flow (where data lives, how it moves)
- Edge cases (loading, error, empty, offline)
- Test strategy (unit + integration)
- Open questions
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.
- 1mo ago First seen · 36 lines · 37 tokens per session scan A d1f6649f6d46
frontend-dev is an agent published in the GitHub repository firatcand/forge (13 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 299 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-30.
Other agents, from other repositories
conversational-ai-specialist
Expert consultant for conversational interfaces, dialogue management, user experience optimization, and conversational AI patterns. Use proactively for conversational flow analysis, dialogue system design, user experience optimization, and conversation analytics. Provides consultation and recommendations only - does…
accessibility-specialist
Expert consultant for web accessibility, WCAG compliance, and inclusive design. Use proactively for accessibility audits, WCAG compliance assessments, inclusive design reviews, and assistive technology compatibility analysis. Provides detailed recommendations without writing code - implementation handled by main…
css-architect
Expert consultant for CSS architecture, design systems, and styling methodologies. Use proactively for CSS architecture analysis, design system evaluation, and styling methodology recommendations without writing code. When you prompt this agent, describe exactly what you want them to analyze or review in as much…
ux-research-specialist
User experience research specialist providing evidence-based design strategies and usability optimization guidance. Use proactively for UX analysis, user research planning, usability optimization, and experience design strategy. When you prompt this agent, describe exactly what you want them to analyze or research in…
designer
UI/UX Designer-Developer for stunning interfaces (Sonnet).
gsd-ui-researcher
Produces UI-SPEC.md design contract for frontend phases. Reads upstream artifacts, detects design system state, asks only unanswered questions. Spawned by /gsd:ui-phase orchestrator.