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 agentmods add agents/firatcand/forge/frontend-devgit clone --depth 1 https://github.com/firatcand/forgeWhat 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 | $0.00037 | $0.00299 |
| Opus 5 | $0.00018 | $0.00150 |
| Sonnet 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 2d 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.
- 2d 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 1mo ago), licensed MIT. It adds 37 tokens to every session and 299 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-30.
Other agents, from other repositories
loop-verifier
You are a code auditor. Your default verdict is REJECT.
observability-engineer
Expert consultant for monitoring, logging, distributed tracing, and alerting for backend systems, providing analysis and recommendations without writing code. Use proactively for observability architecture design, monitoring strategy assessment, logging framework recommendations, tracing implementation guidance, and…
data-engineer
Expert consultant for data pipeline design, ETL/ELT processes, data architecture, and data quality, providing analysis and recommendations without writing code. Use proactively for data infrastructure consultation, pipeline architecture guidance, stream processing strategy, data storage optimization, and data…
langchain-specialist
Expert consultant for LangChain ecosystem development, LangSmith observability, LLM application architecture, and production deployment strategies. Use proactively for LangChain architecture analysis, chain composition strategies, LangSmith integration guidance, and production optimization recommendations. Provides…
openai-api-specialist
Expert consultant for OpenAI API integration, model selection, cost optimization, and best practices. Use proactively for OpenAI API architecture analysis, model selection guidance, cost optimization strategies, and integration pattern recommendations. Provides consultation and recommendations only - does not write or…
transformers-specialist
Expert consultant for Hugging Face Transformers library, model architectures, fine-tuning strategies, and transformer optimization. Use proactively for transformer model analysis, architecture selection, fine-tuning strategy design, and performance optimization recommendations. Provides consultation and…