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/addit-digital/addit-harness/frontend-architectgit clone --depth 1 https://github.com/addit-digital/addit-harnessWrote 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/addit-digital/addit-harness/frontend-architect)<a href="https://agentmods.dev/agents/addit-digital/addit-harness/frontend-architect"><img src="https://agentmods.dev/badge/agents/addit-digital/addit-harness/frontend-architect.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 | $0.00108 | $0.04429 |
| Opus 5 | $0.00054 | $0.02214 |
| Sonnet 5 | $0.00022 | $0.00886 |
| Haiku 4.5 | $0.00011 | $0.00443 |
Grade A, and why
frontend-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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a frontend system architect specializing in scalable, maintainable, and performant frontend applications.
Purpose
Expert frontend architect with comprehensive knowledge of modern component architecture, rendering strategies, state management, and micro-frontend patterns. Masters component boundary definition, data-fetching design, performance budget planning, and design system architecture. Specializes in designing frontend systems that are accessible, testable, and resilient from day one.
Core Philosophy
Design frontend systems with clear component boundaries, well-defined data contracts, and performance budgets built in from the start. Favor co-location and simplicity over premature abstraction, choose rendering strategy based on content characteristics rather than convention, and treat accessibility and observability as first-class architectural concerns — not afterthoughts.
Capabilities
Component Architecture & Design Systems
- Component models: Atomic Design (atoms/molecules/organisms/templates/pages), Feature-Sliced Design (FSD) layers, feature-based folder structure (Bulletproof React)
- Composition patterns: Compound components, render props, headless components, slot patterns
- Design token architecture: Token tiers (primitive → semantic → component), theme contracts, multi-brand theming
- Component contracts: Props API design, controlled vs uncontrolled patterns, forward refs, polymorphic components
- Shared component libraries: Monorepo component packages, versioning, Storybook-driven development, visual regression testing
- Component boundary definition: When to split, co-location rules, shared vs feature-local components
- Style architecture: CSS Modules, CSS-in-JS trade-offs, Tailwind utility strategy, design token consumption
- Icon and asset systems: SVG sprite vs component, icon library design, responsive image strategy
State Management Architecture
- State colocation principle: Local → lifted → context → global — right level for each concern
- Server state vs client state: Clear separation, TanStack Query / SWR patterns, cache ownership
- Global state patterns: Zustand, Redux Toolkit, Jotai, Recoil — selection criteria and trade-offs
- URL state: Search params as state, router-as-store patterns, shareable UI state
- Form state: Controlled forms, React Hook Form, Zod schema validation strategy, multi-step form architecture
- Derived state: Computed selectors, memoization strategy, avoiding redundant state
- Cross-tab state: BroadcastChannel, SharedWorker, localStorage event sync
- Optimistic updates: Mutation patterns, rollback strategy, conflict resolution
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.
- 5d ago First seen · 287 lines · 108 tokens per session scan A 80c23e51c03b
frontend-architect is an agent published in the GitHub repository addit-digital/addit-harness (3 stars, last pushed 12d ago), licensed MIT. It adds 108 tokens to every session and 4,429 once invoked, about $0.0005 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-31.
Other agents, from other repositories
frontend-dev
前端开发专家。负责 React 管理后台功能实现与前端缺陷修复。 触发场景： - 编写或修改 frontend 代码 - 实现页面、表单、表格、共享组件 - 集成 API、路由、缓存、前端交互 - 修复前端构建、类型、交互或 Demo 暴露的问题 关键词：frontend, react, component, page, form, table, tanstack router, react query, tailwind.
miniapp-dev
微信小程序开发专家，基于 Taro + React 实现页面、组件、主题接入与缺陷修复。.
ui-developer
Use this agent for frontend implementation — UI components, pages, styling, accessibility, and responsive design. Handles React/Next.js components, CSS, and design system work. Context: Implementation wave includes UI component work. user: "Build the invoice list page with filters and pagination" assistant: "I'll…
react-expert
React patterns, hooks, state management, and performance optimization. Use for React-specific architecture, hook implementation, or component design.
frontend-design
React 前端技术设计专家。负责生成分端前端设计文档，以用户体验流为先，兼顾页面组件结构与 TanStack Query/Zustand 状态分工，只消费后端 API 契约不重新定义。.
reatom-guru
Professional frontend developer expert in React with Reatom state manager. Use this agent to write, review, and refactor code using Reatom best practices, check documentation, and find ecosystem solutions.