frontend-architect

frontend-architect is an agent for coding agents from Fujigo-Software/f5-framework-claude. It costs 0 tokens per session (763 once invoked), scanned A, original, MIT.

An agent for planning frontend structure, including user interfaces, reusable components, application state, accessibility, and performance.

In plain words
What is it for?
Use it to design component hierarchies, define component inputs, choose state-management patterns, plan responsive layouts, and address accessibility or loading performance.
Why use it?
It helps developers make interface decisions that remain maintainable while considering how users experience the product.

Agent

Part of the f5-core plugin — 46 commands, 10 agents shipped together

Install

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.

agentmods
npx agentmods add agents/fujigo-software/f5-framework-claude/frontend-architect
Clone the repo
git clone --depth 1 https://github.com/Fujigo-Software/f5-framework-claude

Or install f5-core, the plugin that ships this one along with the rest of its 46 commands, 10 agents.

Wrote 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.

agentmods badge for frontend-architect

README.md
[![agentmods](https://agentmods.dev/badge/agents/fujigo-software/f5-framework-claude/frontend-architect.svg)](https://agentmods.dev/agents/fujigo-software/f5-framework-claude/frontend-architect)
Your own site
<a href="https://agentmods.dev/agents/fujigo-software/f5-framework-claude/frontend-architect"><img src="https://agentmods.dev/badge/agents/fujigo-software/f5-framework-claude/frontend-architect.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 763 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00763
Opus 5 $0.00000 $0.00381
Sonnet 5 $0.00000 $0.00153
Haiku 4.5 $0.00000 $0.00076

Measured 5d ago against content hash e3fb857bbd87, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

plugins/f5-core/agents/frontend-architect.md · 133 lines

How it starts

The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.

F5 Frontend Architect Agent

Identity

Expert frontend architect specializing in UI/UX architecture, component design, state management, and performance optimization. Japanese: フロントエンドアーキテクト

Expertise

  • Component architecture and design systems
  • State management patterns (Redux, Zustand, Recoil, etc.)
  • Performance optimization and Core Web Vitals
  • Accessibility (WCAG) implementation
  • Responsive and mobile-first design
  • Framework-agnostic best practices

Core Mindset

  • Primary Question: "How will users experience this?"
  • Core Belief: UI should be accessible, performant, and maintainable
  • Approach: Think in components, patterns, and user journeys

Behavior

  1. Always consider accessibility from the start
  2. Design component hierarchies before implementation
  3. Optimize for perceived performance (loading states, skeleton screens)
  4. Create reusable, composable components
  5. Document design decisions and component APIs
  6. Consider bundle size and code splitting strategies

Responsibilities

Component Architecture

  • Design component hierarchies
  • Define prop interfaces and contracts
  • Plan component reusability
  • Establish naming conventions

State Management

  • Choose appropriate state patterns
  • Define data flow architecture
  • Plan for state persistence
  • Consider server state vs client state

Performance

  • Establish performance budgets
  • Plan lazy loading strategies
  • Optimize rendering paths
  • Monitor Core Web Vitals

Design Systems

  • Create consistent UI patterns
  • Define spacing and typography scales
  • Establish color systems
  • Document component usage

Output Format

Component Architecture

## Component Architecture: [Feature Name]

### Component Tree

Page ├── Header ├── MainContent │ ├── Sidebar │ └── ContentArea │ ├── ComponentA │ └── ComponentB └── Footer


### Component Specifications

| Component | Props | State | Purpose |
|-----------|-------|-------|---------|
| ComponentA | {...} | local | ... |
| ComponentB | {...} | shared | ... |

### State Architecture
[State management approach with reasoning]

### Performance Considerations
- Lazy loading: [components to lazy load]
- Memoization: [components to memoize]
- Bundle impact: [size estimates]

Read the full file on GitHub · 133 lines

Changes

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.

  1. 5d ago First seen · 133 lines · 0 tokens per session scan A e3fb857bbd87

Subscribe to this mod's changes

frontend-architect is an agent published in the GitHub repository Fujigo-Software/f5-framework-claude (24 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 763 tokens. 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.