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 skills add sukirman1901/frontend-expert --skill fe-architecturegit clone --depth 1 https://github.com/sukirman1901/frontend-expertWrote 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/skills/sukirman1901/frontend-expert/fe-architecture)<a href="https://agentmods.dev/skills/sukirman1901/frontend-expert/fe-architecture"><img src="https://agentmods.dev/badge/skills/sukirman1901/frontend-expert/fe-architecture/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/skills/sukirman1901/frontend-expert/fe-architecture"><img src="https://agentmods.dev/badge/skills/sukirman1901/frontend-expert/fe-architecture.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.00050 | $0.00491 |
| Opus 5 | $0.00025 | $0.00246 |
| Sonnet 5 | $0.00010 | $0.00098 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
fe-architecture 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 9d 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
FE Architecture
Overview
Keep UI modular and owned. Prefer local state and server cache over inventing a global store.
When to use
- Greenfield folder layout
- Refactors of tangled components
- Debates: Redux vs context vs query vs URL
When to skip
- Single-file prototype the user wants kept flat
- Pure visual polish with no structure ask
MUST (agent decisions)
| Decision | Default |
|---|---|
| Folders | Feature cohesion (features/x/) over dumping everything in components/ |
| Remote data | Query/loader (data-fetching) — not a global store of server entities |
| URL state | Shareable filters/tabs in the URL |
| Global store | Last resort — only after local → lift → URL → server cache → context |
| File size | Split presentational files >~200 lines; colocated tests when testing |
Workflow
- Boundaries — feature folders over type-only dumps
- State ladder — local → lifted → URL → server cache → context (theme/auth) → global store last
- Server/client — fetch on server when the stack allows; mark client islands explicitly
- Deps — UI primitives don’t import feature screens; features may use shared UI
- Size — split files >200 lines; colocated tests
Agent boundaries
- May decide: Feature vs route folder names; query lib; whether auth lives in context/session
- Must not: Add Redux/Zustand “by default”; put every form field in a global store; create circular feature imports
Checklist
- Feature ownership clear
- No unnecessary global store
- Server state not duplicated in client stores without reason
- Shared UI stays presentational
- State ladder documented in handoff when non-trivial
Depth
references/fe-architecture.md + existing references/architecture.md.
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.
- 9d ago First seen · 60 lines · 50 tokens per session scan A 1711a16f335d
fe-architecture is a skill published in the GitHub repository sukirman1901/frontend-expert (10 stars, last pushed 6d ago), licensed MIT. It adds 50 tokens to every session and 491 once invoked, about $0.0003 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 skills, from other repositories
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
menu-transitions-rtl
Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…