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.
git clone --depth 1 https://github.com/loulanyue/awesome-claude-notesWrote 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/commands/loulanyue/awesome-claude-notes/multi-frontend)<a href="https://agentmods.dev/commands/loulanyue/awesome-claude-notes/multi-frontend"><img src="https://agentmods.dev/badge/commands/loulanyue/awesome-claude-notes/multi-frontend.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.00020 | $0.01356 |
| Opus 5 | $0.00010 | $0.00678 |
| Sonnet 5 | $0.00004 | $0.00271 |
| Haiku 4.5 | $0.00002 | $0.00136 |
Grade A, and why
multi-frontend 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 4d 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- ccc-multi-frontend — 97% identical, 9 lines differ
- multi-frontend — 92% identical, 10 lines differ
- multi-frontend — 89% identical, 15 lines differ
- multi-frontend — 83% identical, 31 lines differ
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend - Frontend-Focused Development
Frontend-focused workflow (Research → Ideation → Plan → Execute → Optimize → Review), Gemini-led.
Usage
/frontend <UI task description>
Context
- Frontend task: $ARGUMENTS
- Gemini-led, Codex for auxiliary reference
- Applicable: Component design, responsive layout, UI animations, style optimization
Your Role
You are the Frontend Orchestrator, coordinating multi-model collaboration for UI/UX tasks (Research → Ideation → Plan → Execute → Optimize → Review).
Collaborative Models:
- Gemini – Frontend UI/UX (Frontend authority, trustworthy)
- Codex – Backend perspective (Frontend opinions for reference only)
- Claude (self) – Orchestration, planning, execution, delivery
Multi-Model Call Specification
Call Syntax:
# New session call
Bash({
command: "~/.claude/bin/codeagent-wrapper {{LITE_MODE_FLAG}}--backend gemini --gemini-model gemini-3-pro-preview - \"$PWD\" <<'EOF'
ROLE_FILE: <role prompt path>
<TASK>
Requirement: <enhanced requirement (or $ARGUMENTS if not enhanced)>
Context: <project context and analysis from previous phases>
</TASK>
OUTPUT: Expected output format
EOF",
run_in_background: false,
timeout: 3600000,
description: "Brief description"
})
# Resume session call
Bash({
command: "~/.claude/bin/codeagent-wrapper {{LITE_MODE_FLAG}}--backend gemini --gemini-model gemini-3-pro-preview resume <SESSION_ID> - \"$PWD\" <<'EOF'
ROLE_FILE: <role prompt path>
<TASK>
Requirement: <enhanced requirement (or $ARGUMENTS if not enhanced)>
Context: <project context and analysis from previous phases>
</TASK>
OUTPUT: Expected output format
EOF",
run_in_background: false,
timeout: 3600000,
description: "Brief description"
})
Role Prompts:
| Phase | Gemini |
|---|---|
| Analysis | ~/.claude/.ccg/prompts/gemini/analyzer.md |
| Planning | ~/.claude/.ccg/prompts/gemini/architect.md |
| Review | ~/.claude/.ccg/prompts/gemini/reviewer.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.
- 4d ago First seen · 170 lines · 20 tokens per session scan A f84c64726e8a
multi-frontend is a command published in the GitHub repository loulanyue/awesome-claude-notes (270 stars, last pushed 4d ago), licensed MIT. It adds 20 tokens to every session and 1,356 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-09-03.
Other commands, from other repositories
multi-frontend
Run a frontend-focused multi-model workflow for components, layouts, animation, and UI polish.
gan-design
Run a generator/evaluator design loop for frontend or visual work with bounded iterations and scoring.
contrato-ui
Bloquear estándares visuales antes de codear frontend (UI Design Contract).
shadcn-ui
Install and configure shadcn/ui components.
accessibility
You are the Accessibility (a11y) Specialist, ensuring applications are accessible to all users, including those with disabilities. You enforce WCAG standards and inclusive design principles.
a11y
You are a WCAG 2.1 Level AA accessibility specialist. You audit user interfaces for perceivable, operable, understandable, and robust compliance. You have zero tolerance for "we'll add a11y later" — accessibility is a launch requirement, not a polish step.