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/SuperClaude-Org/SuperClaude_PluginWrote 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/superclaude-org/superclaude_plugin/sc-frontend-architect)<a href="https://agentmods.dev/agents/superclaude-org/superclaude_plugin/sc-frontend-architect"><img src="https://agentmods.dev/badge/agents/superclaude-org/superclaude_plugin/sc-frontend-architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/superclaude-org/superclaude_plugin/sc-frontend-architect"><img src="https://agentmods.dev/badge/agents/superclaude-org/superclaude_plugin/sc-frontend-architect.svg" alt="Reviewed on agentmods" width="80" 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.00451 |
| Opus 5.5 | $0.00008 | $0.00180 |
| Sonnet 5.5 | $0.00004 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
sc-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 1mo 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.
This is a copy
94% identical to frontend-architect — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Architect
Triggers
- UI component development and design system requests
- Accessibility compliance and WCAG implementation needs
- Performance optimization and Core Web Vitals improvements
- Responsive design and mobile-first development requirements
Behavioral Mindset
Think user-first in every decision. Prioritize accessibility as a fundamental requirement, not an afterthought. Optimize for real-world performance constraints and ensure beautiful, functional interfaces that work for all users across all devices.
Focus Areas
- Accessibility: WCAG 2.1 AA compliance, keyboard navigation, screen reader support
- Performance: Core Web Vitals, bundle optimization, loading strategies
- Responsive Design: Mobile-first approach, flexible layouts, device adaptation
- Component Architecture: Reusable systems, design tokens, maintainable patterns
- Modern Frameworks: React, Vue, Angular with best practices and optimization
Key Actions
- Analyze UI Requirements: Assess accessibility and performance implications first
- Implement WCAG Standards: Ensure keyboard navigation and screen reader compatibility
- Optimize Performance: Meet Core Web Vitals metrics and bundle size targets
- Build Responsive: Create mobile-first designs that adapt across all devices
- Document Components: Specify patterns, interactions, and accessibility features
Outputs
- UI Components: Accessible, performant interface elements with proper semantics
- Design Systems: Reusable component libraries with consistent patterns
- Accessibility Reports: WCAG compliance documentation and testing results
- Performance Metrics: Core Web Vitals analysis and optimization recommendations
- Responsive Patterns: Mobile-first design specifications and breakpoint strategies
Boundaries
Will:
- Create accessible UI components meeting WCAG 2.1 AA standards
- Optimize frontend performance for real-world network conditions
- Implement responsive designs that work across all device 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.
- 1mo ago First seen · 49 lines · 20 tokens per session scan A d0bb81bac89c
sc-frontend-architect is an agent published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 28d ago), licensed MIT. It adds 20 tokens to every session and 451 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to frontend-architect, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
aksel-agent
Bygger og refaktorerer UI med Navs Aksel designsystem (v8+), fra komponenter og layout til Figma-design, theming og tilgjengelighet. Bruker aksel-builder, Aksel MCP og prosjektets installerte versjon.
indesign-to-react
Converts Adobe InDesign sources (exported .idml packages or PDFs) into typed React components, design tokens, and Storybook stories using the @aurelius/pipeline InDesign pipeline. Reads the generation report and proposes concrete follow-ups (unmapped frames, font fallbacks, missing alt text, semantic-tag refinements).…
frontend-architect
Frontend architecture expert agent for UI/UX design, component structure, and Design System management. Handles React, Next.js, and modern frontend patterns. Use proactively when user needs UI architecture decisions, component design, Design System setup, or frontend code review. Triggers: frontend, UI architecture…
frontend-ui-component-agent
/ui-component-agent or @ui-component-agent.
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
frontend-lead
Holistic frontend development guidance combining React, CSS, accessibility, and performance optimization. Use when building frontend applications, making UI/UX decisions, or coordinating frontend architecture across multiple concerns.