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/diillson/chatcli/frontend-specialistgit clone --depth 1 https://github.com/diillson/chatcliWhat 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.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 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.
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.
- 3d ago First seen · 556 lines · 63 tokens per session scan A 508379b69e03
frontend-specialist is an agent published in the GitHub repository diillson/chatcli (89 stars, last pushed 3d ago), licensed Apache-2.0. 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
implementer
Milestone executor. Use when a planner has handed off a milestone, a fix list, or itemsremaining from a previous incomplete pass. Codes, tests, repairs. Returns what's done, what's remaining, and a completion score. Never replans, never judges.
planner
Planning agent. Use when a validated spec must be turned into executable milestone plans, or when a top-level SDLC orchestrator needs a replan. Writes plans and decisions only. Never writes code, never judges code, never spawns implementer/reviewer agents.
react-architect
Use this agent when you need expert guidance on React application architecture, component design, performance optimization, or code quality improvements. This agent is specifically tuned for this project's tech stack (Tauri v2, React 19, shadcn/ui v4, Tailwind v4, Zustand v5, Vitest v3) and should be used for…
ui-design-expert
Use this agent when you need expert UI/UX design guidance for Tauri React applications, including component design, layout improvements, accessibility enhancements, or creating native-feeling desktop experiences. Examples: Context: User is building a Tauri app and wants to improve the visual design of their dashboard…
generate_agent
Generates a customized agent based on user-defined parameters.
react-coder
Use this agent when you need to create or modify React components following the project's simplicity-first philosophy. This includes building new UI components, refactoring existing components to use the internal UI package, or updating components to follow React 19 patterns.