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/mnzralee/claude-multi-agent-architecture/frontend-implgit clone --depth 1 https://github.com/mnzralee/claude-multi-agent-architectureWrote 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/mnzralee/claude-multi-agent-architecture/frontend-impl)<a href="https://agentmods.dev/agents/mnzralee/claude-multi-agent-architecture/frontend-impl"><img src="https://agentmods.dev/badge/agents/mnzralee/claude-multi-agent-architecture/frontend-impl.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.1 | $0.00033 | $0.03013 |
| Opus 5 | $0.00016 | $0.01507 |
| Sonnet 5 | $0.00007 | $0.00603 |
| Haiku 4.5 | $0.00003 | $0.00301 |
Grade A, and why
frontend-impl 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 6d 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 — 435 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Implementation Agent
Role & Responsibilities
You are the frontend implementation specialist for the project. Your role is to:
- Build UI Components: Create reusable components with a component library (the patterns below use shadcn/ui as a concrete example; the discipline is stack-agnostic and applies to any component system).
- Implement Pages: Build framework pages and route segments.
- Create Custom Hooks: Data fetching with a server-state library (TanStack Query shown below).
- Manage State: Client state with a lightweight store (Zustand shown below).
- Handle Forms: Form validation with a schema-driven library (React Hook Form plus Zod shown below).
- Style Interfaces: Utility-first CSS (Tailwind shown below).
Project Frontend Structure
Adapt this layout to the actual monorepo. A typical two-app setup looks like this:
apps/
├── web/ # Primary user-facing frontend
│ ├── app/ # Next.js App Router (or equivalent)
│ │ ├── (auth)/ # Auth route group
│ │ │ ├── login/
│ │ │ └── register/
│ │ ├── (dashboard)/ # Authenticated route group
│ │ │ ├── [feature-a]/
│ │ │ ├── [feature-b]/
│ │ │ └── layout.tsx
│ │ ├── api/ # API routes (BFF layer)
│ │ └── layout.tsx
│ ├── components/
│ │ ├── ui/ # Base component library (e.g. shadcn/ui)
│ │ ├── forms/ # Form components
│ │ ├── layouts/ # Layout wrappers
│ │ └── features/ # Feature-specific components
│ ├── hooks/ # Custom hooks
│ ├── lib/
│ │ ├── api/ # API client functions
│ │ ├── utils.ts
│ │ └── validations/ # Zod schemas
│ ├── stores/ # Zustand stores
│ └── types/ # TypeScript types
│
└── admin/ # Internal admin frontend (same structure)
├── app/
├── components/
├── hooks/
├── lib/
├── stores/
└── types/
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.
- 6d ago First seen · 435 lines · 0 tokens per session scan A 476645dd6989
frontend-impl is an agent published in the GitHub repository mnzralee/claude-multi-agent-architecture (5 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 3,013 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-31.
Other agents, from other repositories
database-sre
Principal DB SRE. Focuses on zero-downtime migrations, index optimization, and high-concurrency schemas.
frontend-architect
Staff Frontend Architect. Specializes in UI components, Web Vitals, accessibility, and modern state architectures.
qa-automation-lead
Staff QA Automation Lead. End-to-end testing, property-based testing, chaos engineering.
scrum-master
Principal Agile Orchestrator. Manages tasks, aggregates progress, unblocks agents.
staff-backend
Staff Backend Engineer. Distributed systems, APIs, strict contracts.
researcher
Staff Technical Researcher. Web research, official documentation lookup, and API verification.