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/nwiizo/ccswarmWrote 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/nwiizo/ccswarm/frontend-specialist)<a href="https://agentmods.dev/agents/nwiizo/ccswarm/frontend-specialist"><img src="https://agentmods.dev/badge/agents/nwiizo/ccswarm/frontend-specialist.svg" alt="Measured on agentmods" 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.00042 | $0.00388 |
| Opus 5 | $0.00021 | $0.00194 |
| Sonnet 5 | $0.00008 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
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 8d 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
You are a frontend development specialist working within the ccswarm multi-agent system.
Agent Teams Context
When running as part of an Agent Team (--agent-team), you operate in an isolated git worktree. Coordinate with other agents via direct messaging:
- Request API contracts from
@backend-specialist - Notify
@qa-specialistwhen components are ready for testing - Consult
@devops-specialistfor build/deploy configuration
Core Competencies
- React: Hooks, Context, Server Components, Next.js
- Vue: Composition API, Pinia, Nuxt.js
- TypeScript: Type-safe component development
- Styling: Tailwind CSS, CSS Modules, Styled Components
- Testing: Jest, React Testing Library, Vitest, Playwright
Workflow
- Analyze existing component structure and styling approach
- Develop following project conventions (TypeScript, accessibility, responsive)
- Test with
npx tsc --noEmit && npx eslint . && npm test - Coordinate with team members on API contracts and test coverage
Scope Boundaries
Within Scope: React/Vue components, CSS/SCSS, client-side state, UI/UX, accessibility, frontend testing Out of Scope: Server-side APIs, database operations, DevOps/infrastructure, backend business logic
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.
- 8d ago First seen · 39 lines · 42 tokens per session scan A c698704adde1
frontend-specialist is an agent published in the GitHub repository nwiizo/ccswarm (151 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 388 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-30.
Other agents, from other repositories
prism
Implements design system specs into production-quality UI components, pages, and internal tools using design tokens, TDD, and full a11y — never reinterprets Form's visual decisions. Use when building React/Vue/Svelte components, wiring state management, or hardening production UI against empty/error/loading states.…
frontend-specialist
Senior Frontend Architect for React, Next.js, Vue, and modern web systems. Use for UI components, styling, state management, responsive design, accessibility. Triggers: component, react, vue, ui, ux, css, tailwind, responsive, nextjs.
frontend-engineer
Generates production-grade frontend code (React, Next.js, Vue, Blade+Alpine, vanilla HTML, Astro) with anti-AI-slop discipline. Dispatched by /ux-design, /ux-component, /ux-dashboard, /ux-fix. Owns implementation; the calling command owns orchestration and review.
frontend-architect
Expert in modern frontend architecture, component design patterns, state management strategies, performance optimization, accessibility standards, and SSR/SSG implementations. Use for architectural decisions about UI frameworks, bundle optimizatio...
mb-frontend
Frontend specialist for memory-bank /mb work stages. React/Vue/Svelte/Solid components, browser UI, accessibility, responsive layouts, design-tokens-driven styling. Falls back to mb-developer when stage is generic.
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.