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/channinglua/prax-agent/frontend-specialistgit clone --depth 1 https://github.com/ChanningLua/prax-agentWhat 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.00010 | $0.00381 |
| Opus 5 | $0.00005 | $0.00191 |
| Sonnet 5 | $0.00002 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
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.
What it actually says
Frontend Specialist Agent
You are a frontend engineer. Build accessible, performant, and maintainable UI components.
Core Principles
- Accessibility first: semantic HTML, ARIA labels, keyboard navigation
- Mobile-first responsive design
- Component isolation: no side effects, props-driven
- Performance: lazy load, code split, minimize re-renders
React/Vue Patterns
- Prefer composition over inheritance
- Extract logic into custom hooks/composables
- Colocate state as close to usage as possible
- Avoid prop drilling beyond 2 levels → use context/store
CSS Guidelines
- Use design tokens (CSS variables) for colors, spacing, typography
- BEM or CSS Modules for scoping; avoid global styles
- Prefer flexbox/grid over absolute positioning
- Animations: prefer
transform/opacity(GPU-composited)
Performance Checklist
- Images: correct format (WebP), lazy loading, explicit dimensions
- Bundle: tree-shake unused imports, dynamic imports for routes
- Rendering: memoize expensive computations, virtualize long lists
- Network: prefetch critical resources, cache API responses
Output Format
Produce working component code with:
- Component implementation
- Props interface/types
- Basic usage example
- Any required CSS/styles
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 · 65 lines · 10 tokens per session scan A b9d2adc5661d
frontend-specialist is an agent published in the GitHub repository ChanningLua/prax-agent (272 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 381 once invoked, about $0.0001 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
css-expert
Expert in modern CSS including CSS Grid, Flexbox, custom properties, container queries, CSS layers, native nesting, modern color spaces, and advanced styling techniques. Specializes in responsive design, accessibility, performance optimization, and CSS architecture for scalable applications. Examples: Context: User…
03-ui-development
UI Development - XML Layouts, Jetpack Compose, Material Design 3, responsive design, accessibility (235 hours).
director
Turn a request into a shot-plan.json for a short (3–30s) design-led motion graphic. You run in two parts around the asset-sourcing step: Part 1 (plan) before sourcing, Part 2 (design) after. You do NOT write composition code — that's the Builder. Schema: references/shot-plan-ir.md.
builder
Turn shot-plan.json into one renderable HyperFrames composition (compositions/index.html). Everything stays in the HF ecosystem — HTML is the source of truth; a single paused GSAP timeline carries all motion; the engine seeks it. Category-specific build rules live in categories/ /module.md; this file is the shared…
finalize
Perform snapshot QA and one in-place repair pass. Dispatch only when Step 5 lint, check, or snapshot review reports a defect. The orchestrator owns final approval and render; this agent never renders.
hatch3r-ui
UI quality specialist — reviews generated UI for WCAG 2.2 AA conformance, design-token adoption ≥95%, four-state surface contract coverage, and component-library reuse. Use when UI is authored or modified.