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/niclejeune/pi-agents-config/frontend-developergit clone --depth 1 https://github.com/niclejeune/pi-agents-configWrote 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/niclejeune/pi-agents-config/frontend-developer)<a href="https://agentmods.dev/agents/niclejeune/pi-agents-config/frontend-developer"><img src="https://agentmods.dev/badge/agents/niclejeune/pi-agents-config/frontend-developer.svg" alt="Measured on agentmods" 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 | $0.00037 | $0.00329 |
| Opus 5 | $0.00018 | $0.00164 |
| Sonnet 5 | $0.00007 | $0.00066 |
| Haiku 4.5 | $0.00004 | $0.00033 |
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 5d 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
Original Claude model hint:
sonnet. Pi model mapped togpt-5.5/ thinkingmedium.
You are running as a pi-teams teammate. Work independently, keep outputs concise, update task status when applicable, and send clear progress/final messages back to the team lead. 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.
- 5d ago First seen · 37 lines · 37 tokens per session scan A 5dad4feb28d4
frontend-developer is an agent published in the GitHub repository niclejeune/pi-agents-config (2 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 329 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-31.
Other agents, from other repositories
ui-builder
Builds React/Next.js UI components with accessibility and responsive design.
next-js-architect
Next.js 14 App Router architecture specialist. Validates server vs client component boundaries, data fetching patterns, server action usage, and import layering. Dispatch when touching app/ directory, data fetching, mutations, or component boundaries.
react-architect
React 18 + React Query + Zustand architecture specialist. Validates component structure, store patterns, hook design, and import layering. Dispatch when touching component hierarchy, store shape, data fetching, or cross-feature state.
frontend-engineer
Frontend specialist for muggle-ai-ui. Implements UI slices, runs quality gates, returns structured summaries.
frontend-engineer
Implements and reviews frontend code — React, Vue, Svelte, Web Components, plain HTML/CSS. Handles state management, component APIs, accessibility baseline, responsive layouts, and user-facing performance. Use when the task involves UI, client-side state, forms, routing, or rendering behavior.
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…