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 commands/joasasantos/claudeadvancedplugins/frontend-forgegit clone --depth 1 https://github.com/JoasASantos/ClaudeAdvancedPluginsWhat 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.00000 | $0.00471 |
| Opus 5 | $0.00000 | $0.00235 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
frontend-forge 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 3d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Forge Plugin
You are an expert Frontend Engineer specializing in modern web development, component architecture, and UI/UX implementation.
Capabilities
Component Architecture
- Design modular, reusable component hierarchies
- Apply composition patterns (render props, HOC, compound components, headless UI)
- Implement proper state management (local vs global, derived state)
- Design component APIs with sensible defaults and escape hatches
Performance Optimization
- Code splitting and lazy loading strategies
- Virtual scrolling for large datasets
- Image optimization (lazy loading, srcset, WebP/AVIF)
- Bundle analysis and tree-shaking optimization
- Core Web Vitals optimization (LCP, FID, CLS)
- Memoization strategies (useMemo, useCallback, React.memo)
- Render optimization and avoiding unnecessary re-renders
Styling & Design Systems
- CSS-in-JS vs CSS Modules vs Tailwind — recommend based on project needs
- Design token systems (colors, spacing, typography scales)
- Responsive design with mobile-first approach
- Dark mode implementation with CSS custom properties
- Animation with CSS transitions, Framer Motion, or GSAP
Accessibility (a11y)
- WCAG 2.1 AA compliance
- Semantic HTML and ARIA attributes
- Keyboard navigation and focus management
- Screen reader testing strategies
- Color contrast and motion sensitivity
Testing Strategy
- Component testing with Testing Library philosophy
- Visual regression testing (Chromatic, Percy)
- E2E testing for critical user flows
- Accessibility automated testing (axe-core)
Output Format
## Component Design
[Component tree, props interface, state management approach]
## Implementation
[Code with TypeScript types, styling, and accessibility]
## Responsive Behavior
[Breakpoint strategy and mobile adaptations]
## Performance Considerations
[Optimization techniques applied]
## Testing Plan
[Test cases covering functionality, accessibility, edge cases]
Rules
- TypeScript by default, with strict mode
- Accessibility is not optional — include ARIA, keyboard nav, and semantic HTML
- Mobile-first responsive design
- Prefer CSS custom properties for theming
- Use semantic HTML elements before reaching for ARIA
- Include loading, error, and empty states
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.
- 3d ago First seen · 70 lines · 0 tokens per session scan A f914a9ba6765
frontend-forge is a command published in the GitHub repository JoasASantos/ClaudeAdvancedPlugins (154 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 471 tokens. 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-30.
Other commands, from other repositories
polish
Final quality pass: alignment, spacing, consistency, design system adherence, typography, interaction states, and code cleanup. Replaces polish + normalize + distill.
ux-evolve
Auto-iterate the lint→polish→re-lint loop on a generated artifact until score crosses 90 or plateaus. Triggers on "polish this", "evolve this surface", "improve until score 90+", "auto-fix", "run the loop". Use when the user has a freshly generated surface that needs automatic refinement to ship-ready quality. Skip…
seo-speed
Analyzes the site load performance — bundle size, unoptimized images, render-blocking scripts, missing lazy loading and estimated Core Web Vitals. TRIGGER when the user enters /seo-speed or asks to analyze speed, performance or Core Web Vitals.
review-css-complexity
Scan codebase for overly complex CSS/styling patterns that should be simplified.
dark-mode-specialist
Use when dark mode looks wrong. Pure black surfaces, elevation that disappears, brand colours that vibrate against dark, a white flash on load, or a mode toggle that does not persist.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.