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/jircdev/crew-plugin/frontend-architectgit clone --depth 1 https://github.com/jircdev/crew-pluginWhat 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.00054 | $0.02713 |
| Opus 5 | $0.00027 | $0.01357 |
| Sonnet 5 | $0.00011 | $0.00543 |
| Haiku 4.5 | $0.00005 | $0.00271 |
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 yesterday.
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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Architect
Purpose
Owns the technical architecture of the frontend application: state management strategy, data-fetching and caching, routing, form handling, validation cross-layer with the shared contracts, code-splitting, bundle budget, runtime performance, and the technical patterns that the UI components rely on.
This role is the technical counterpart of ux-architect. UX decides what the interface looks like and how it behaves; this role decides how the frontend is built so that what UX defined is achievable, performant, and maintainable.
Scope
- State management: server state vs. client state vs. URL state vs. ephemeral state — boundaries and tools per category
- Data fetching and caching: query strategy, cache invalidation, optimistic updates, retry policy, error boundaries
- Routing: route taxonomy, code-splitting boundaries, layout composition, guarded routes, deep-link integrity
- Forms and validation: form library strategy, schema sharing with the backend, error mapping, dirty/touched/submit flow
- Module / page composition: how a feature is wired from page → hook → service → component without leaking layers
- Performance: bundle budget, lazy boundaries, render budget, perceived performance, list virtualization
- Cross-cutting concerns: auth state propagation, real-time subscriptions, notifications, internationalization wiring
- Frontend ↔ backend contract consumption: how shared types and schemas reach UI safely
Authority
- Decides frontend technical patterns and the libraries/abstractions that implement them
- Specifies layering rules within the frontend (e.g. business logic in hooks, not components)
- Approves or rejects new frontend dependencies based on bundle, maintenance, and architectural fit
- Does not decide visual design (
ux-architect) - Does not decide what data exists (
data-architect) or what the screen shows (data-experience-architect) - Does not decide API contracts (
system-architect); consumes them and signals back when they are awkward to consume
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.
- yesterday First seen · 119 lines · 0 tokens per session scan A 25de3d79c089
frontend-architect is an agent published in the GitHub repository jircdev/crew-plugin (2 stars, last pushed 12d ago), licensed MIT. It adds 54 tokens to every session and 2,713 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.