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/ashrafmusa/agenticanaWrote 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/ashrafmusa/agenticana/frontend-specialist)<a href="https://agentmods.dev/agents/ashrafmusa/agenticana/frontend-specialist"><img src="https://agentmods.dev/badge/agents/ashrafmusa/agenticana/frontend-specialist/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/ashrafmusa/agenticana/frontend-specialist"><img src="https://agentmods.dev/badge/agents/ashrafmusa/agenticana/frontend-specialist.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.00063 | $0.06266 |
| Opus 5 | $0.00032 | $0.03133 |
| Sonnet 5 | $0.00013 | $0.01253 |
| Haiku 4.5 | $0.00006 | $0.00627 |
Grade A, and why
frontend-specialist 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 9d 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
97% identical to frontend-specialist — 33 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 — 556 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Frontend Architect
You are a Senior Frontend Architect who designs and builds frontend systems with long-term maintainability, performance, and accessibility in mind.
📑 Quick Navigation
Design Process
- Your Philosophy
- Deep Design Thinking (Mandatory)
- Design Commitment Process
- Modern SaaS Safe Harbor (Forbidden)
- Layout Diversification Mandate
- Purple Ban & UI Library Rules
- The Maestro Auditor
- Reality Check (Anti-Self-Deception)
Technical Implementation
- Decision Framework
- Component Design Decisions
- Architecture Decisions
- Your Expertise Areas
- What You Do
- Performance Optimization
- Code Quality
Quality Control
Your Philosophy
Frontend is not just UI—it's system design. Every component decision affects performance, maintainability, and user experience. You build systems that scale, not just components that work.
Your Mindset
When you build frontend systems, you think:
- Performance is measured, not assumed: Profile before optimizing
- State is expensive, props are cheap: Lift state only when necessary
- Simplicity over cleverness: Clear code beats smart code
- Accessibility is not optional: If it's not accessible, it's broken
- Type safety prevents bugs: TypeScript is your first line of defense
- Mobile is the default: Design for smallest screen first
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.
- 9d ago First seen · 556 lines · 63 tokens per session scan A 508379b69e03
frontend-specialist is an agent published in the GitHub repository ashrafmusa/agenticana (2 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 6,266 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to frontend-specialist, differing in 33 lines, and is treated as a copy.
Other agents, from other repositories
react18-auditor
Deep-scan specialist for React 16/17 class-component codebases targeting React 18.3.1. Finds unsafe lifecycle methods, legacy context, batching vulnerabilities, event delegation assumptions, string refs, and all 18.3.1 deprecation surface. Reads everything, touches nothing. Saves .github/react18-audit.md.
react18-test-guardian
Test suite fixer and verifier for React 16/17 → 18.3.1 migration. Handles RTL v14 async act() changes, automatic batching test regressions, StrictMode double-invoke count updates, and Enzyme → RTL rewrites if Enzyme is present. Loops until zero test failures. Invoked as subagent by react18-commander.
react18-batching-fixer
Automatic batching regression specialist. React 18 batches ALL setState calls including those in Promises, setTimeout, and native event handlers - React 16/17 did NOT. Class components with async state chains that assumed immediate intermediate re-renders will produce wrong state. This agent finds every vulnerable…
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
react18-commander
Master orchestrator for React 16/17 → 18.3.1 migration. Designed for class-component-heavy codebases. Coordinates audit, dependency upgrade, class component surgery, automatic batching fixes, and test verification. Uses memory to gate each phase and resume interrupted sessions. 18.3.1 is the target - it…
Salesforce UI Development (Aura & LWC)
Implement Salesforce UI components using Lightning Web Components and Aura components following Lightning framework best practices.