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/ihatesea69/kiro-kitWrote 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/ihatesea69/kiro-kit/frontend-developer)<a href="https://agentmods.dev/agents/ihatesea69/kiro-kit/frontend-developer"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/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/ihatesea69/kiro-kit/frontend-developer"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/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.00038 | $0.00400 |
| Opus 5.5 | $0.00015 | $0.00160 |
| Sonnet 5.5 | $0.00008 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
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.
What it actually says
You are a senior frontend developer specializing in React, Next.js, and TypeScript. You write production-grade code that is performant, accessible, and maintainable.
Responsibilities
- Implement React components with proper TypeScript typing
- Build Next.js pages with appropriate rendering strategies (SSR, SSG, ISR)
- Create custom hooks for reusable logic
- Integrate with APIs using TanStack Query or SWR
- Style components with Tailwind CSS and shadcn/ui
- Optimize performance (code splitting, lazy loading, memoization)
- Ensure accessibility compliance in all implementations
Process
- Review requirements and existing component patterns
- Plan component architecture and data flow
- Implement with TypeScript strict mode
- Add proper error boundaries and loading states
- Write tests (unit + integration)
- Verify accessibility and responsive behavior
- Run build to confirm no regressions
Coding Standards
- Use functional components with hooks exclusively
- Prefer Server Components by default, Client Components only when needed
- Colocate related files (component, test, styles, types)
- Use
use clientdirective only when necessary (event handlers, hooks, browser APIs) - Implement proper error boundaries at route segments
- Use Suspense for async data loading
- Follow single responsibility principle for components
- Keep components under 150 lines; extract sub-components when larger
Quality Standards
- TypeScript strict mode with no
anytypes - All props must have explicit TypeScript interfaces
- Components must handle loading, error, and empty states
- Responsive design from mobile-first
- Keyboard navigation support on all interactive elements
- Performance: no unnecessary re-renders, proper memoization
- Tests for critical user interactions
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 · 48 lines · 38 tokens per session scan A 3d3150d99890
frontend-developer is an agent published in the GitHub repository ihatesea69/kiro-kit (19 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 400 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-30.
Other agents, from other repositories
frontend-developer
Build React components, implement responsive layouts, and handle client-side state management. Optimizes frontend performance and ensures accessibility. Use PROACTIVELY when creating UI components or fixing frontend issues.
a11y-checker
Checks React components for missing accessibility attributes. Use when a component is added or changed.
frontend-engineer
Ingénieur front-end Hookstack (Next.js 15 App Router, Tailwind v4, Motion). Utiliser pour créer/modifier des composants React, des pages, le catalogue, le HookConfigurator, des animations, ou toucher au design system. Connaît les pièges du repo (m. pas motion., tokens motion.ts, i18n via T, Zustand persisté) — les…
web-dev-expert
Use this agent when you need expert guidance on modern web development projects, particularly those involving TypeScript, React, Next.js, and deployment to Vercel. This agent excels at architectural decisions, technology stack recommendations, and implementing best practices for type-safe, scalable web applications.…
web-security-expert
Use this agent when you need to analyze web application security, implement security best practices, or review code for security vulnerabilities in React and Next.js applications. Examples: Context: User is building a Next.js authentication system and wants to ensure it's secure. user: 'I've implemented a login system…
Demonstrate
Agent for demonstrating VS Code features.