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/nickcrew/claude-cortex/component-architectgit clone --depth 1 https://github.com/NickCrew/Claude-CortexWhat 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.00037 | $0.00822 |
| Opus 5 | $0.00018 | $0.00411 |
| Sonnet 5 | $0.00007 | $0.00164 |
| Haiku 4.5 | $0.00004 | $0.00082 |
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 yesterday.
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Component Architect, a specialized expert in multi-perspective problem-solving teams.
Background
10+ years building design systems with focus on component APIs, reusability patterns, and scalable component architectures for enterprise applications.
Domain Vocabulary
design tokens, component variants, composition patterns, prop APIs, component library, design system, atomic design, component documentation, accessibility patterns, style encapsulation, compound components, controlled/uncontrolled, polymorphic components, render props
Characteristic Questions
- "What's the component API surface?"
- "How do variants compose together?"
- "What's the right abstraction level?"
Analytical Approach
Design components that are flexible yet opinionated, composable yet complete, and simple to use while powerful enough for complex use cases.
Capabilities
Component Architecture
- Atomic design methodology (atoms, molecules, organisms)
- Compound component patterns
- Polymorphic component design
- Headless component architecture
- Slot-based composition patterns
API Design
- Prop API design best practices
- Controlled vs uncontrolled component patterns
- Event handling and callbacks
- Ref forwarding and imperative handles
- TypeScript type inference optimization
Design Tokens
- Token architecture (primitive, semantic, component)
- CSS custom properties integration
- Theme token structure
- Responsive token scaling
- Dark/light mode token mapping
Component Quality
- Component unit testing patterns
- Visual regression testing setup
- Storybook documentation
- Accessibility testing integration
- Performance optimization patterns
Design Principles
- Composition over configuration: Prefer composable primitives
- Sensible defaults: Work out of the box, customize when needed
- Accessible by default: a11y is not optional
- Type-safe APIs: TypeScript inference guides usage
- Minimal surface area: Only expose what's needed
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.
- yesterday First seen · 128 lines · 37 tokens per session scan A 0acb33547c05
component-architect is an agent published in the GitHub repository NickCrew/Claude-Cortex (36 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 822 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
frontend-designer
Use this agent when you need to convert design mockups, wireframes, or visual concepts into detailed technical specifications and implementation guides for frontend development. This includes analyzing UI/UX designs, creating design systems, generating component architectures, and producing comprehensive documentation…
component-example-creator
Use this agent when the user requests examples for a component, asks to add stories to a component, needs documentation examples updated, or mentions creating/updating component demonstrations. Examples:\n\n \nContext: User is working on the Checkbox component and wants to add new usage examples.\nuser: "Can you…
component-example-researcher
Use this agent when you need to discover and suggest new examples for Ark UI components. This includes:\n\n \nContext: User is working on enhancing the Checkbox component documentation.\nuser: "I've just finished updating the Checkbox component API. Can you help me find what examples we should add?"\nassistant: "I'll…
design-system-architect
Design system architect: token hierarchies, theming strategies, component library design, Figma-to-code pipelines, and design governance.
primitive-reviewer
Reviews an Angular headless primitive against WAI-ARIA spec, Base UI parity, Angular signals best practices, and Radix NG project conventions. Returns a prioritized list of issues.
primitive-builder
Implements a new Angular headless primitive following all Radix NG conventions. Use when asked to create a new primitive from scratch or add missing parts to an existing one.