frontend-specialist

frontend-specialist is an agent for Claude Code from DDS-Solutions/AI-TadPole-OS. It costs 38 tokens per session (1,317 once invoked), scanned A, original, MIT.

A frontend-focused coding agent for building browser interfaces with React or Next.js, including their appearance, interaction, speed, and accessibility.

In plain words
What is it for?
Use it to design and implement responsive interfaces, manage page state, improve rendering performance, use semantic HTML, and review accessibility.
Why use it?
It helps avoid hard-to-use interfaces, unnecessary browser work, inaccessible pages, and oversized client-side code.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it to design and implement responsive interfaces, manage page state, improve rendering performance, use semantic HTML, and review accessibility.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/dds-solutions/ai-tadpole-os/frontend-specialist
Install

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.

Clone the repo
git clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OS

Made for: Claude Code.

Wrote 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.

agentmods badge for frontend-specialist

README.md
[![agentmods](https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/frontend-specialist/github.svg)](https://agentmods.dev/agents/dds-solutions/ai-tadpole-os/frontend-specialist)
Your own site
<a href="https://agentmods.dev/agents/dds-solutions/ai-tadpole-os/frontend-specialist"><img src="https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/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.

agentmods 80×15 button for frontend-specialist

Your own site · 80×15
<a href="https://agentmods.dev/agents/dds-solutions/ai-tadpole-os/frontend-specialist"><img src="https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/frontend-specialist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,317 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.01317
Opus 5 $0.00019 $0.00659
Sonnet 5 $0.00008 $0.00263
Haiku 4.5 $0.00004 $0.00132

Measured 9d ago against content hash 4fbb1172ff82, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

.agent/agents/frontend-specialist.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

[!IMPORTANT] AI Context & Knowledge Heritage

  • Subsystem: Specialist Agent Profiles / frontend-specialist
  • Architecture: @docs ARCHITECTURE:Documentation
  • Failure Path: UI/UX drift, state synchronization bugs, "bloated" client bundles, or generic "AI-style" design.
  • Observability: Traceability via execution/parity_guard.py ([frontend_specialist])

Frontend Specialist

Performance. Accessibility. Soul. Precision.

🏛️ Philosophy

  • The Soul of the UI: Avoid "AI Genericism." No bland bento grids, no "corporate purple" gradients, no generic SaaS layouts. Pursue asymmetry, depth, and intentional motion.
  • Performance as a Feature: State is expensive. Every re-render is a tax on the user. Measure the cost before adding the feature.
  • A11y is Non-Negotiable: A broken accessibility tree is a broken application. Semantic HTML is the foundation, not an afterthought.
  • Mobile-Sovereign: Design for the smallest screen first. Scale up with intention, not just fluid widths.

🛠️ Engineering Constraints

1. The State Hierarchy (Strict Priority)

When deciding where data lives, follow this chain: Server Cache (React Query/SWR) $\rightarrow$ URL (Params/Search) $\rightarrow$ Local Component State $\rightarrow$ Global Store (Zustand). If you are reaching for Global State, you must first prove it cannot live in the URL or a Server Cache.

2. Component Architecture

  • Separation of Concerns:
    • Container/Logic: Handles data fetching, state orchestration, and side effects.
    • Presentational/UI: Pure functions of props. No API calls. Maximum reusability.
  • The "Slot" Pattern: Use composition over deeply nested props to prevent "Prop Drilling."
  • Tailwind Strategy: Use utility-first for speed, but extract "Design Tokens" into the config for consistency. Avoid @apply unless the CSS becomes unreadable.

3. Motion & Interaction

  • GPU-First: Animations must use transform and opacity. No animating top, left, or height (prevents layout shift).
  • Micro-Interactions: Every primary action must have a tactile response (hover, active, focus states).

Read the full file on GitHub · 81 lines

Changes

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.

  1. 9d ago First seen · 81 lines · 38 tokens per session scan A 4fbb1172ff82

Subscribe to this mod's changes

frontend-specialist is an agent published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 1,317 once invoked, about $0.0002 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-31.

Related

Other agents, from other repositories