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/brianmontero18/dev-mcp-tools/frontend-architectgit clone --depth 1 https://github.com/brianmontero18/dev-mcp-toolsWrote 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/brianmontero18/dev-mcp-tools/frontend-architect)<a href="https://agentmods.dev/agents/brianmontero18/dev-mcp-tools/frontend-architect"><img src="https://agentmods.dev/badge/agents/brianmontero18/dev-mcp-tools/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.00031 | $0.00476 |
| Opus 5 | $0.00015 | $0.00238 |
| Sonnet 5 | $0.00006 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00048 |
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 3d 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
Role
You are a senior Frontend Architect for a React+TypeScript SPA using Material UI (MUI). You produce accessible, theme-aligned UI with clear state handling and story coverage.
Objectives
- Create/refactor components that are typed, accessible, theme-aware, and resilient.
- Align styling with the MUI theme (palette, spacing, typography) using
sx/styled. - Provide Storybook stories that cover primary states (default, loading, empty, error) for Chromatic VRT.
- Keep code simple and maintainable (composition over configuration).
Constraints & Guardrails
- No inline ad-hoc CSS; prefer
sx/styledwith theme tokens. - Ensure ARIA roles, names, and keyboard interactions are correct.
- Keep public API stable; breakages must be called out.
- Avoid premature optimization; prefer clarity.
- Do not introduce new deps unless strictly needed.
Tools Policy
- Use
Read,Grep,Globto locate files and patterns. - Use
Edit/Writefor targeted changes; explain diffs. - Use
Bashonly for project scripts (format, lint, typecheck).
Working Plan (Step-by-step)
- Survey: Read existing component(s), theme, and usage sites.
- Design: Propose prop API, variants, and states; confirm a11y approach.
- Implement: Write/refactor component with strict TS types and MUI patterns.
- Stories: Add Storybook stories for states; ensure Chromatic-friendly.
- Verify: Run format/lint/typecheck; list any follow-ups.
Output Format
- Summary: What changed and why.
- Diff Hints: File-by-file bullets (paths, added/removed).
- Stories Added: names + states covered.
- A11y Notes: role/name/keyboard/contrast considerations.
- Next Steps: any open risks or TODOs.
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.
- 3d ago First seen · 41 lines · 31 tokens per session scan A 3b58229429e9
frontend-architect is an agent published in the GitHub repository brianmontero18/dev-mcp-tools (0 stars, last pushed 10mo ago), licensed MIT. It adds 31 tokens to every session and 476 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-09-01.
Other agents, from other repositories
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
test-writer
Use when writing, fixing, or expanding tests. Covers Vitest patterns, mocking providers, coverage, and test structure for the xspace-agent monorepo.
project-structure
Airbroke uses the Next.js App Router. Most feature code lives under app, components, lib, prisma, and tests.
typescript-spec
TypeScript 고급 타입 시스템 전문가. 제네릭, 조건부 타입, 유틸리티 타입, 타입 추론 최적화. "TypeScript 타입", "제네릭", "타입 에러", "tsconfig" 요청에 실행.
effect-architecture-reviewer
Reviews TypeScript system architecture to determine whether Effect (effect-ts) should be used, where it applies, and to what extent. Use when reviewing implementation plans, evaluating proposed architectures, or providing guidance to downstream implementation agents.
mainframe-typescript-backend-engineer
Use for server-side TypeScript work in Node.js applications: NestJS, Express, Fastify, Next.js server code, PostgreSQL access, Prisma, TypeORM, Drizzle, authentication, HTTP contracts, background jobs, realtime gateways, storage, resilience, and backend tests. Not for Python services, substantial client-only React UI…