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 skills add ihatesea69/kiro-kit --skill frontend-developmentgit 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/skills/ihatesea69/kiro-kit/frontend-development)<a href="https://agentmods.dev/skills/ihatesea69/kiro-kit/frontend-development"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/frontend-development.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.1 | $0.00035 | $0.00348 |
| Opus 5 | $0.00017 | $0.00174 |
| Sonnet 5 | $0.00007 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
frontend-development 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 4d 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
Frontend Development
Activate this skill when implementing React/Next.js features with TypeScript.
When to Use
- Implementing React components (Server or Client)
- Creating custom hooks for reusable logic
- Setting up data fetching with TanStack Query or SWR
- Managing application state (Zustand, Jotai, or React Context)
- Optimizing rendering performance
- Implementing form handling with React Hook Form + Zod
React Patterns
- Prefer Server Components by default; use Client Components only when needed
- Use composition over prop drilling
- Implement error boundaries at route segments
- Use Suspense for async data loading
- Keep components focused (single responsibility)
- Extract complex logic into custom hooks
TypeScript Standards
- Strict mode enabled, no
anytypes - Explicit prop interfaces for all components
- Use generics for reusable utilities
- Discriminated unions for complex state
- Proper event handler typing (React.MouseEvent, etc.)
Data Fetching
- Server Components: fetch directly with proper caching
- Client Components: TanStack Query or SWR for cache management
- Implement optimistic updates for mutations
- Handle loading, error, and empty states explicitly
- Use Suspense boundaries for streaming
Performance
- Dynamic imports for route-level code splitting
- React.memo only where measured benefit exists
- useMemo/useCallback for expensive computations or stable references
- Virtualize long lists (TanStack Virtual)
- Optimize images with next/image
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.
- 4d ago First seen · 51 lines · 35 tokens per session scan A 70057e3bec97
frontend-development is a skill published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 19d ago), licensed MIT. It adds 35 tokens to every session and 348 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-09-03.
Other skills, from other repositories
open-slide-best-practices
Best practices for authoring presentations with open-slide, the React slide framework with a fixed 1920×1080 canvas, with full Hebrew and RTL support. Covers the slides/[id]/index.tsx file contract, type scale, DesignSystem tokens, themes/ system, @slide-comment inspector markers, current.json deictic resolution…
hipson-creative-frontend-motion-architect
Use for premium creative frontend, motion UI, scroll-driven animation, scrollytelling, cinematic landing pages, microinteractions, and implementation-ready prompts for React/Next.js frontend agents.
agent-frontend-patterns
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.
algolia-search
Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuning Use when: adding search to, algolia, instantsearch, search api, search functionality.
empty-trigger-short-circuit-before-app-state
Skip nested memory collection when no triggers exist so render-bound getAppState() is never invoked unnecessarily.
design-agent
You are the Design agent for this project. You own React components, page routes, design tokens, and visual layout.