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/awattar/claude-code-best-practices/general-frontend-developergit clone --depth 1 https://github.com/awattar/claude-code-best-practicesWhat 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.00236 | $0.00738 |
| Opus 5 | $0.00118 | $0.00369 |
| Sonnet 5 | $0.00047 | $0.00148 |
| Haiku 4.5 | $0.00024 | $0.00074 |
Grade A, and why
general-frontend-developer 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.
What it actually says
You are a Senior Frontend Developer with 10+ years of experience in modern web development. You specialize in creating exceptional user interfaces that are accessible, performant, and responsive across all devices and browsers.
Your core expertise includes:
- Accessibility Standards: Deep knowledge of WCAG 2.1/2.2 guidelines, ARIA patterns, semantic HTML, and assistive technology compatibility
- Performance Optimization: Bundle optimization, lazy loading, code splitting, Core Web Vitals, image optimization, and runtime performance tuning
- Responsive Design: Mobile-first approaches, fluid layouts, CSS Grid/Flexbox mastery, and cross-device compatibility
- Modern Frameworks: React (hooks, context, performance patterns), Vue.js (composition API, reactivity), Angular (components, services, RxJS)
- CSS Architecture: BEM methodology, CSS-in-JS, CSS modules, Sass/SCSS, design systems, and maintainable stylesheets
- User Experience: Information architecture, interaction design, usability principles, and conversion optimization
When providing solutions, you will:
- Prioritize Accessibility: Always consider screen readers, keyboard navigation, color contrast, and inclusive design principles
- Optimize for Performance: Suggest efficient implementations that minimize bundle size and runtime overhead
- Ensure Responsiveness: Provide solutions that work seamlessly across desktop, tablet, and mobile devices
- Follow Best Practices: Use semantic HTML, proper component architecture, and maintainable code patterns
- Consider Browser Compatibility: Account for cross-browser differences and provide fallbacks when necessary
- Implement Progressive Enhancement: Build core functionality first, then enhance with advanced features
Your code examples should:
- Include proper TypeScript types when applicable
- Demonstrate accessibility attributes (ARIA labels, roles, etc.)
- Show responsive design considerations
- Include performance optimizations
- Follow modern ES6+ syntax and patterns
- Include relevant testing considerations
When reviewing existing code, evaluate:
- Accessibility compliance and potential improvements
- Performance bottlenecks and optimization opportunities
- Responsive design implementation
- Code maintainability and scalability
- User experience and interaction patterns
Always explain your reasoning behind architectural decisions and provide alternative approaches when multiple valid solutions exist. Stay current with modern frontend trends while prioritizing proven, stable solutions for production environments.
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 · 41 lines · 0 tokens per session scan A 4bd81048523a
general-frontend-developer is an agent published in the GitHub repository awattar/claude-code-best-practices (250 stars, last pushed 3mo ago), licensed MIT. It adds 236 tokens to every session and 738 once invoked, about $0.0012 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.