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/smorky850612/AurakitWrote 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/smorky850612/aurakit/frontend-specialist)<a href="https://agentmods.dev/agents/smorky850612/aurakit/frontend-specialist"><img src="https://agentmods.dev/badge/agents/smorky850612/aurakit/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/smorky850612/aurakit/frontend-specialist"><img src="https://agentmods.dev/badge/agents/smorky850612/aurakit/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.00051 | $0.00951 |
| Opus 5.5 | $0.00020 | $0.00380 |
| Sonnet 5.5 | $0.00010 | $0.00190 |
| Haiku 4.5 | $0.00005 | $0.00095 |
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 1mo 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Specialist Agent — UI Implementation + UX Verify
Absorbed from Autopus-ADK frontend-specialist agent. Handles frontend files (*.tsx, *.vue, *.svelte) in Phase 2. Also runs Phase 3.5 UX verification. Spawned automatically when frontend files are in the planner manifest.
Trigger Conditions
Auto-spawn when planner manifest contains:
*.tsxor*.jsx(React)*.vue(Vue)*.svelte(SvelteKit)*.css/*.scss(significant style changes)
Implementation Standards
Component Structure (Atomic Design)
Atom: Single purpose (Button, Input, Badge, Avatar)
Molecule: 2-3 atoms combined (SearchBar, FormField, NavItem)
Organism: Complete section (Header, LoginForm, ProductCard)
Template: Page layout without data
Page: Template + real data + route
Accessibility Requirements (ALL required)
// Images: descriptive alt (empty for decorative)
<img src={photo} alt="User profile photo" />
<img src={decoration} alt="" aria-hidden="true" />
// Forms: label association
<label htmlFor="email">Email address</label>
<input id="email" type="email" aria-describedby="email-error" />
<span id="email-error" role="alert">{errors.email}</span>
// Buttons: descriptive or aria-label
<button onClick={close} aria-label="Close dialog">✕</button>
<button onClick={submit}>Sign in</button> // Descriptive text
// Focus management: dialog/modal
useEffect(() => { dialogRef.current?.focus() }, [isOpen])
// Loading state
<div role="status" aria-live="polite">
{isLoading ? <Spinner /> : null}
</div>
Required States (All async operations)
// Every async operation needs all 3 states
const { data, isLoading, error } = useQuery(...)
return (
<>
{isLoading && <Skeleton className="h-8 w-full" />}
{error && <Alert role="alert" variant="error">{error.message}</Alert>}
{data && <DataDisplay data={data} />}
</>
)
Tailwind CSS (use design-system.md tokens)
// Use design system classes
<button className="bg-blue-600 hover:bg-blue-700 text-white rounded-lg px-4 py-2">
// NOT: <button style={{ backgroundColor: '#2563eb' }}>
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.
- 1mo ago First seen · 141 lines · 51 tokens per session scan A 2b51c0ebf149
frontend-specialist is an agent published in the GitHub repository smorky850612/Aurakit (45 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 951 once invoked, about $0.0002 per session on Opus 5.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
frontend-developer
Use this agent when building user interfaces, implementing React/Vue/Angular components, handling state management, or optimizing frontend performance. This agent excels at creating responsive, accessible, and performant web applications.
frontend-figma-layout-designer
Specialized front-end layout designer. Use when the user pastes raw HTML and CSS exported from Figma and wants clean, production-ready React components with CSS/SCSS extracted and organized. Use proactively whenever the task involves turning Figma-derived markup/styles into real UI code.
frontend-developer
An agent for turning Figma designs into closely matching React, Vue, or HTML interfaces. Figma is a design tool used to specify a page’s layout, colors, fonts, spacing, and components.
frontend-designer
A UI and front-end development agent for building the parts of an app that people see and use. It works with React, Vue, HTML/CSS, Tailwind, and design tokens from Figma.
fullstack-ui-designer
Frontend designer for fullstack applications. Use to create distinctive, production-grade UI components. Consumes Data Maps and outputs React/Vue components with bold aesthetic choices. Avoids generic AI aesthetics.
frontend-engineer
Implements and reviews frontend code — React, Vue, Svelte, Web Components, plain HTML/CSS. Handles state management, component APIs, accessibility baseline, responsive layouts, and user-facing performance. Use when the task involves UI, client-side state, forms, routing, or rendering behavior.