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 agentmods add agents/ihatesea69/kiro-kit/component-architectgit clone --depth 1 https://github.com/ihatesea69/kiro-kitWhat 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 | $0.00032 | $0.00386 |
| Opus 5 | $0.00016 | $0.00193 |
| Sonnet 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 2d 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.
- 2d 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 (18 stars, last pushed 13d ago), licensed MIT. It adds 32 tokens to every session and 386 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-08-30.
Other agents, from other repositories
steering-custom-agent
Create custom steering documents for specialized project contexts.
spec-design-agent
Generate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process.
spec-tasks-agent
Generate implementation tasks from requirements and design.
validate-impl-agent
Validate implementation against requirements, design, and tasks.
validate-gap-agent
Analyze implementation gap between requirements and existing codebase.
Frontend Developer
Expert frontend developer specializing in Next.js, React, TypeScript, and modern UI development.