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 seandkendall/kiro-config --skill react-frontend-patternsgit clone --depth 1 https://github.com/seandkendall/kiro-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/skills/seandkendall/kiro-config/react-frontend-patterns)<a href="https://agentmods.dev/skills/seandkendall/kiro-config/react-frontend-patterns"><img src="https://agentmods.dev/badge/skills/seandkendall/kiro-config/react-frontend-patterns/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/skills/seandkendall/kiro-config/react-frontend-patterns"><img src="https://agentmods.dev/badge/skills/seandkendall/kiro-config/react-frontend-patterns.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.00045 | $0.01234 |
| Opus 5.5 | $0.00018 | $0.00494 |
| Sonnet 5.5 | $0.00009 | $0.00247 |
| Haiku 4.5 | $0.00005 | $0.00123 |
Grade A, and why
react-frontend-patterns 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 today.
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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Frontend Patterns
Component Template
/** Dashboard page — displays financial overview with charts and recent transactions. */
interface DashboardProps {
userId: string;
}
export function Dashboard({ userId }: DashboardProps) {
const { data, isLoading, error } = useQuery({
queryKey: ['dashboard', userId],
queryFn: fetchDashboard,
});
if (isLoading) return <DashboardSkeleton />;
if (error) return <ErrorState message="Failed to load dashboard" />;
if (!data) return <EmptyState message="No data yet" />;
return (
<main data-testid="dashboard-page">
<h1 className="text-2xl font-bold">Dashboard</h1>
{/* content */}
</main>
);
}
Form Pattern (react-hook-form + zod)
const schema = z.object({
amount: z.number().positive('Must be greater than 0'),
description: z.string().min(1, 'Required'),
});
function TransactionForm() {
const {
register,
handleSubmit,
formState: { errors },
} = useForm({ resolver: zodResolver(schema) });
return (
<form onSubmit={handleSubmit(onSubmit)} data-testid="transaction-form">
<label htmlFor="amount">Amount</label>
<input
id="amount"
type="number"
aria-invalid={!!errors.amount}
aria-describedby="amount-error"
{...register('amount', { valueAsNumber: true })}
/>
{errors.amount && (
<p id="amount-error" role="alert">
{errors.amount.message}
</p>
)}
</form>
);
}
State Management
- Server state: TanStack Query (useQuery, useMutation, optimistic updates)
- Client state: Zustand for global UI state, React Context for theme/auth
- Never prop-drill more than 2 levels
Accessibility Checklist
- All interactive elements keyboard-reachable (Tab, Enter, Space, Escape)
- Visible focus indicators — never
outline: nonewithout replacement - Color contrast: 4.5:1 normal text, 3:1 large text
- All images have
alttext (decorative:alt="") - Form inputs have
<label>oraria-label - Error messages use
role="alert" - NEVER use browser
alert(),confirm(), orprompt()dialogs — for ANY purpose: informational messages, error/success notifications, confirmations, or approval prompts. Always use a modal component instead (shadcn/uiDialogfor messages/notifications,AlertDialogfor confirmations/approvals that block on a user decision)
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.
- today First seen · 130 lines · 45 tokens per session scan A eedd290fb0b5
react-frontend-patterns is a skill published in the GitHub repository seandkendall/kiro-config (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session and 1,234 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-10-27.
Other skills, from other repositories
aws-cdk
AWS CDK infrastructure development in TypeScript. Use when creating stacks, constructs, L2/L3 patterns, CDK testing, synth/deploy pipelines or organizing IaC code.
aws-lambda-typescript
AWS Lambda development with TypeScript. Use when writing Lambda handlers, bundling with esbuild, using AWS SDK v3/Powertools, strict typing or optimizing Node.js Lambda performance.
typescript-runtime
TypeScript toolchain configuration and best practices. Use when setting up tsconfig, ESLint, Prettier, Vitest, bundling, type patterns or TypeScript project standards.
sandy
Run TypeScript scripts in sandboxed microVMs or Docker containers with AWS SDK access via IMDS. Use when investigating AWS resources, running read-only queries, or executing TypeScript automation that needs AWS credentials.
zustand-docs
Zustand — small, fast, scalable state management for React. Store creation, hooks, middleware, TypeScript.
aws-cdk-builder
AWS CDK infrastructure builder using TypeScript with L2/L3 constructs and Well-Architected patterns. Activate on: AWS CDK, CDK construct, CDK stack, CDK pipeline, AWS infrastructure as code TypeScript, L2 construct, CDK patterns. NOT for: Terraform IaC (use terraform-module-builder), Kubernetes manifests (use…