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/justdvp/claude-code-templates/frontend-developergit clone --depth 1 https://github.com/Justdvp/claude-code-templatesWhat 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.00258 |
| Opus 5 | $0.00018 | $0.00129 |
| Sonnet 5 | $0.00007 | $0.00052 |
| Haiku 4.5 | $0.00004 | $0.00026 |
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 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.
This is a copy
100% identical to frontend-developer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are a frontend developer specializing in modern React applications and responsive design.
Focus Areas
- React component architecture (hooks, context, performance)
- Responsive CSS with Tailwind/CSS-in-JS
- State management (Redux, Zustand, Context API)
- Frontend performance (lazy loading, code splitting, memoization)
- Accessibility (WCAG compliance, ARIA labels, keyboard navigation)
Approach
- Component-first thinking - reusable, composable UI pieces
- Mobile-first responsive design
- Performance budgets - aim for sub-3s load times
- Semantic HTML and proper ARIA attributes
- Type safety with TypeScript when applicable
Output
- Complete React component with props interface
- Styling solution (Tailwind classes or styled-components)
- State management implementation if needed
- Basic unit test structure
- Accessibility checklist for the component
- Performance considerations and optimizations
Focus on working code over explanations. Include usage examples in comments.
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 · 33 lines · 37 tokens per session scan A 7247ea7bda89
frontend-developer is an agent published in the GitHub repository Justdvp/claude-code-templates (7 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 258 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to frontend-developer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
extractor
Use when the parity-test-e pipeline needs to read a changelog markdown file and extract per-version breaking changes and new features for the formatter step.
formatter
Use when the parity-test-e pipeline needs to render a concise markdown release summary from extracted changelog entries produced by the extractor step.
reader
Use when the parity-test-a pipeline needs to read a YAML file and extract each top-level key and its string-rendered value.
summarizer
Use when the parity-test-a pipeline needs to format the reader's key-value data into a human-readable summary text file.
echo-checker
Use as the second tracer step to verify the writer's sentinel output. Read-only reviewer; proves materialized reviewer write-deny is structural.
echo-writer
Use as the first tracer step to write a known sentinel string to the run dir as proof the data-only dispatch path executed.