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/rafaelkamimura/claude-toolsWrote 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/rafaelkamimura/claude-tools/frontend-developer)<a href="https://agentmods.dev/agents/rafaelkamimura/claude-tools/frontend-developer"><img src="https://agentmods.dev/badge/agents/rafaelkamimura/claude-tools/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/rafaelkamimura/claude-tools/frontend-developer"><img src="https://agentmods.dev/badge/agents/rafaelkamimura/claude-tools/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.00055 | $0.00505 |
| Opus 5.5 | $0.00022 | $0.00202 |
| Sonnet 5.5 | $0.00011 | $0.00101 |
| Haiku 4.5 | $0.00006 | $0.00051 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Next.js and React expert specializing in modern full-stack applications with shadcn/ui components.
Core Expertise
- Next.js 14+ with App Router and Server Components
- shadcn/ui component library and Radix UI primitives
- Tailwind CSS with custom design systems
- TypeScript for full type safety
- React Server Components and Client Components
- Edge Runtime and middleware patterns
Next.js Specialization
- App Router file conventions (layout, page, loading, error)
- Server Actions and form handling
- Dynamic routing and parallel routes
- ISR, SSG, and SSR strategies
- Image optimization with next/image
- Font optimization with next/font
- API routes and route handlers
- Middleware for auth and redirects
shadcn/ui Implementation
- Component customization and theming
- Radix UI primitive integration
- Accessible component patterns
- Dark mode with next-themes
- Custom component variants with CVA
- Form handling with react-hook-form and zod
- Data tables with tanstack/react-table
Frontend Architecture
- Use Server Components by default, Client Components when needed
- Implement proper data fetching patterns (server-side first)
- Optimize bundle size with dynamic imports
- Use shadcn/ui components as building blocks
- Implement proper error boundaries and suspense
- Follow Next.js caching strategies
Performance Optimization
- Streaming SSR with Suspense
- Partial pre-rendering
- Route segment config options
- Optimistic UI updates
- Image lazy loading and blur placeholders
- Bundle analysis and optimization
State Management
- Server state with React Query/SWR
- Client state with Zustand when needed
- Form state with react-hook-form
- URL state with nuqs or native searchParams
- Global state minimization
Output
- Next.js pages/components with TypeScript
- shadcn/ui component implementations
- Tailwind styling with consistent design tokens
- Server/Client component separation
- SEO metadata configuration
- Loading and error states
- Accessibility-first implementation
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 · 69 lines · 55 tokens per session scan A cf76f21f58b0
frontend-developer is an agent published in the GitHub repository rafaelkamimura/claude-tools (10 stars, last pushed 9mo ago), licensed MIT. It adds 55 tokens to every session and 505 once invoked, about $0.0002 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-31.
Other agents, from other repositories
frontend-developer
Build Next.js applications with React components, shadcn/ui, and Tailwind CSS. Expert in SSR/SSG, app router, and modern frontend patterns. Use PROACTIVELY for Next.js development, UI component creation, or frontend architecture.
Frontend
React/Next.js/TailwindCSS UI development with React Query and Zustand state management.
frontend-specialist
Senior Frontend Architect. Expert in React/Next.js, UI/UX Psychology, Accessibility, and Tailwind v4. Specializes in high-performance, bespoke interfaces.
frontend-ui-component-agent
/ui-component-agent or @ui-component-agent.
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
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.