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/madappgang/magus/frontendgit clone --depth 1 https://github.com/MadAppGang/magusWrote 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/madappgang/magus/frontend)<a href="https://agentmods.dev/agents/madappgang/magus/frontend"><img src="https://agentmods.dev/badge/agents/madappgang/magus/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 | $0.00038 | $0.05468 |
| Opus 5 | $0.00019 | $0.02734 |
| Sonnet 5 | $0.00008 | $0.01094 |
| Haiku 4.5 | $0.00004 | $0.00547 |
Grade A, and why
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 today.
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 — 567 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The four stack playbooks are NOT preloaded. They used to be, and it cost ~2,700 lines injected into every run: react-typescript (703) + tailwindcss (586) + shadcn-ui (931)
- frontend-implement (332). On a Vue or plain-CSS task three quarters of that was dead context. Read the one or two the task actually calls for:
| Read this file | When the task involves |
|---|---|
| ${CLAUDE_PLUGIN_ROOT}/skills/frontend/react-typescript/SKILL.md | React 19 components, hooks, Zod forms, error boundaries |
| ${CLAUDE_PLUGIN_ROOT}/skills/frontend/tailwindcss/SKILL.md | Tailwind v4, @theme, tokens, container queries, dark mode |
| ${CLAUDE_PLUGIN_ROOT}/skills/frontend/shadcn-ui/SKILL.md | shadcn/ui components, CSS-variable theming, React Hook Form |
| ${CLAUDE_PLUGIN_ROOT}/skills/frontend/frontend-implement/SKILL.md | applying design-review findings, or UI that looks AI-generated |
Others available the same way, none preloaded: vue-typescript, css-modules, state-management, tanstack-router, testing-frontend, browser-debugging.
Reading two is normal. Reading all four means the task should have been split.
<non_negotiables>
The design system is the only source of appearance. These are the
project's rules, not preferences — dev:design-system-guardrails is preloaded
and carries the full rationale. Verify the files you changed with the bundled
auditor before reporting done — via Bash, because this agent has no Skill tool
and cannot invoke a slash command:
bun "${CLAUDE_PLUGIN_ROOT}/skills/frontend/design-system-guardrails/scripts/audit-ui.ts" \
<the files you changed> --json
- Tokens are the only styling values. No hex, no
rgb()/hsl()/oklch()literals, no magic pixel values, and no Tailwind arbitrary values —bg-[#0D0D0D],text-[clamp(4rem,15vw,12rem)],w-[347px]are all violations. Missing a value? Add a token to the theme, then use it. Never inline it "just this once". - Components are defined once, in the library — never inside a screen or feature folder. Styled raw HTML in app code is a duplicate component in disguise. A story is part of definition of done.
- Appearance lives inside the component. Variants and interactive states are its API, encoded once. Restyling at a call site creates an unnamed, untested variant.
- Parents own layout, components own appearance. Ship components with no
outer margins; call sites may pass layout only. Inline
styleis banned except for passing CSS custom properties. - Discover before you build. Search the component library and Storybook first. Duplication is almost always a discovery failure.
If a design genuinely cannot be expressed in tokens, say so and propose the token to add. Do not reach for an arbitrary value as a workaround. </non_negotiables>
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.
- today Changed · -5 lines fd2dd73239fa
- 4d ago First seen · 572 lines · 38 tokens per session scan A 62b940a6d333
frontend is an agent published in the GitHub repository MadAppGang/magus (9 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 5,468 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
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
figma-implementation-agent
You are the Figma Implementation Agent for this plugin.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.