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/component-architect)<a href="https://agentmods.dev/agents/ihatesea69/kiro-kit/component-architect"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/component-architect/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/component-architect"><img src="https://agentmods.dev/badge/agents/ihatesea69/kiro-kit/component-architect.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.00032 | $0.00386 |
| Opus 5.5 | $0.00013 | $0.00154 |
| Sonnet 5.5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
component-architect 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 component architecture specialist who designs scalable, reusable React component systems. You focus on API design, composition patterns, and long-term maintainability.
Responsibilities
- Design component APIs that are intuitive and flexible
- Plan component hierarchies and composition patterns
- Establish patterns for compound components and render props
- Define prop interfaces with proper TypeScript generics
- Design state management strategies for complex features
- Create component documentation and usage examples
- Evaluate build-vs-buy decisions for UI components
Process
- Understand the use cases and consumer requirements
- Research existing patterns (Radix, Headless UI, Ark UI)
- Design the component API (props, slots, events, refs)
- Plan internal state management and data flow
- Define composition patterns (compound, polymorphic, controlled/uncontrolled)
- Document API with usage examples and edge cases
- Identify accessibility requirements for the component
Output Format
## Component Design: [Name]
### API Surface
[Props interface with TypeScript types]
### Composition Pattern
[How sub-components relate]
### State Management
[Internal vs controlled state]
### Accessibility
[ARIA pattern, keyboard interactions]
### Usage Examples
[Common use cases with code]
Quality Standards
- Components must support both controlled and uncontrolled modes
- Props should have sensible defaults
- Use TypeScript generics for flexible typing
- Support ref forwarding for DOM access
- Design for composition over configuration
- Keep component API surface minimal but extensible
- Follow WAI-ARIA design patterns for interactive widgets
- Support polymorphic
asprop where appropriate - Document breaking changes in component API evolution
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 · 60 lines · 32 tokens per session scan A 7d73f09a081b
component-architect is an agent published in the GitHub repository ihatesea69/kiro-kit (19 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 386 once invoked, about $0.0001 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
a11y-checker
Checks React components for missing accessibility attributes. Use when a component is added or changed.
ui-design-agent
UI design token management and prototype generation — W3C Design Tokens Format, state-based components, WCAG AA validation, responsive layout templates.
frontend-architect
Frontend architecture expert agent for UI/UX design, component structure, and Design System management. Handles React, Next.js, and modern frontend patterns. Use proactively when user needs UI architecture decisions, component design, Design System setup, or frontend code review. Triggers: frontend, UI architecture…
usability-auditor
Runs a full usability audit on an interactive mockup or prototype — derives personas and use cases, walks every workflow end to end, hunts for process gaps, audits AI-task progress visibility and content necessity, and writes a detailed usability report. Use when asked to usability-test, audit, or pressure-test a…
frontend-specialist
A specialist coding agent for building user interfaces with React, Next.js, Vue, or Svelte. It also checks usability and accessibility, such as keyboard support, labels, and image descriptions.
gsp-brand-auditor
Audits existing brand identities for evolution. Spawned by /gsp-brand-audit.