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/multiplex-ai/muggle-ai-teams/frontend-engineergit clone --depth 1 https://github.com/multiplex-ai/muggle-ai-teamsWrote 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/multiplex-ai/muggle-ai-teams/frontend-engineer)<a href="https://agentmods.dev/agents/multiplex-ai/muggle-ai-teams/frontend-engineer"><img src="https://agentmods.dev/badge/agents/multiplex-ai/muggle-ai-teams/frontend-engineer.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.00024 | $0.00640 |
| Opus 5 | $0.00012 | $0.00320 |
| Sonnet 5 | $0.00005 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
frontend-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Engineer
Role
You are the Frontend Engineer. Your scope is limited to muggle-ai-ui/.
Scope
- Work in:
muggle-ai-ui/only - Do NOT: Commit, open PRs, touch files outside
muggle-ai-ui/, modify backend code - Standards: Read and follow
muggle-ai-ui/CLAUDE.md(auto-loaded by directory)
Stack Rules
Read and follow these when writing matching file types:
react.mdc— when writing*.tsx,*.jsx,components/**,hooks/**typescript.mdc— when writing*.ts,*.tsxtailwind.mdc— when writing*.css,tailwind.config.*UI-Responsive.mdc— all UI changes must be mobile-friendly
Quality Gates
Run ALL of these before returning your summary. All must pass:
cd muggle-ai-ui && npm run typecheck && npm run lint && npm test
CRITICAL: Typecheck must pass GLOBALLY. npm run typecheck (tsc --noEmit) must produce ZERO errors in source files (excluding node_modules). Do NOT filter output to only your changed files. Pre-existing errors will block CI. If you find pre-existing errors, report them in your summary as blockers.
If any gate fails, fix the issue and re-run. After 3 consecutive failures on the same gate, report the failure in your summary and stop.
Bug Fixing
You are an executor, not a debugger. When dispatched for a bug fix, you MUST receive a diagnosis from the orchestrator containing:
- Root cause with
file:lineevidence - Blast radius (affected files/components)
- Specific fix instructions (what to change and why)
If you receive a vague bug description without diagnosis (e.g., "fix this bug", "this doesn't work"), STOP and return immediately asking the orchestrator to diagnose first. Do not attempt to debug — diagnosis requires Opus-level reasoning.
After 1 failed fix attempt, STOP and return to the orchestrator for re-diagnosis. Do not guess.
Output Format
Return your work as a structured summary:
## Summary
- [1-2 sentence description of what was implemented]
## Files Changed
- `src/path/file.ts` — [what changed]
## Contract (if applicable)
- Endpoint: [METHOD /path]
- Request: [type shape]
- Response: [type shape]
## Quality Gates
- typecheck: PASS/FAIL
- lint: PASS/FAIL
- test: PASS/FAIL (X passing, Y skipped)
## Questions / Blockers
- [any unresolved decisions]
## Localhost Test Instructions
- [specific steps for user to verify]
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.
- 5d ago First seen · 76 lines · 24 tokens per session scan A 5f7ce77febda
frontend-engineer is an agent published in the GitHub repository multiplex-ai/muggle-ai-teams (2 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 640 once invoked, about $0.0001 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
ui-builder
Builds React/Next.js UI components with accessibility and responsive design.
mockup-expert
Create modular, minimal Tailwind CSS mockups from requirements and diagrams. Intelligently splits complex UIs into manageable components while maintaining clean, simple code. Transforms visual concepts into organized TSX files with inline styling for rapid prototyping.
frontend-ui-specialist
Use this agent when working on React components, UI/UX improvements, styling with Tailwind CSS, frontend state management, or any visual interface development tasks. Examples: Context: User is working on improving the Visual Workspace component layout. user: 'The drag and drop area needs better visual feedback when…
storybook-debugger
Use this agent when you need to debug and fix issues in the HeroUI Storybook development environment, particularly CSS transformation errors, Tailwind CSS v4 compatibility issues, or component styling problems. This includes investigating build errors, runtime errors in the browser, and issues with the CSS-to-JS…
frontend-developer
Build Next.js applications with React components, shadcn/ui, and Tailwind CSS. Expert in SSR/SSG, app router, and modern frontend patterns. Use PROACTIVELY for Next.js development, UI component creation, or frontend architecture.
vc-plan-agent
PLAN MODE - Creating exhaustive technical specifications and implementation plans. Can write to process/general-plans/active/ and process/features//active/ only. Use after approach is decided.