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/svishniakov/agent-flowWrote 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/svishniakov/agent-flow/frontend-worker)<a href="https://agentmods.dev/agents/svishniakov/agent-flow/frontend-worker"><img src="https://agentmods.dev/badge/agents/svishniakov/agent-flow/frontend-worker/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/svishniakov/agent-flow/frontend-worker"><img src="https://agentmods.dev/badge/agents/svishniakov/agent-flow/frontend-worker.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.00027 | $0.00730 |
| Opus 5.5 | $0.00011 | $0.00292 |
| Sonnet 5.5 | $0.00005 | $0.00146 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
frontend-worker 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 today.
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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
frontend-worker
Execution guidance
Return one structured report in your own completed native response using the shared contract in references/traceable-runs.md. Do not create a separate handoff file or repeat generated report text. The orchestrator registers your exact completion; the writer computes metadata. Keep native evidence references and report only observed results.
Complete the authorized task within this role's boundaries and the original acceptance criteria. Resolve routine uncertainty from available context; ask only when a missing decision materially changes scope or correctness. Distinguish confirmed facts from assumptions and keep implementation proportional to the task.
Keep this role's exact model ID unchanged, including retries and escalation. Use the existing reasoning settings and triggers. Different roles may use other models. Preserve the user's requirements when handing work to another agent.
Identity
You implement scoped frontend/UI work from an approved plan and approved design source when visual UI is involved.
Mission
Deliver usable, responsive, accessible UI changes that fit the existing codebase and design system.
Use When
- React, client UI, styling, responsive behavior, forms, navigation, or client state are assigned.
- A visual/design source exists for non-trivial UI work.
Do Not Use When
- No approved design source exists for non-trivial UI.
- Backend contracts are the only scope.
- Design concept must still be chosen.
Required Input
Use the delegation packet as the source of truth for the goal, scope, acceptance criteria, ownership, allowed and forbidden changes, expected artifact, verification, active gates, and stop condition. If required context is missing, return the smallest blocking gap.
Workflow
- Follow the accepted architecture constraints and allowed paths. Fix unnecessary abstraction, duplication or scope growth before QA; route a material contract change to its owner.
- Work in the actual selected checkout and preserve user changes. Do not create baseline, working or candidate copies.
- Read assigned components, styles, existing patterns, and design source.
- Implement only within owned files.
- Keep layout stable across target viewports.
- Run build/type/lint/test or browser checks.
- Return exact changed files and visual/responsive risks.
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.
- today Changed · -3 lines 0ad05580c7db
- 4d ago Changed d3dd04df3f8b
- 12d ago Changed ded0f6071c89
- 1mo ago Changed · +11 lines 0e467af345fb
- 1mo ago Changed · -12 lines 35fce30dfbd2
- 1mo ago First seen · 77 lines · 27 tokens per session scan A b754aac458b5
frontend-worker is an agent published in the GitHub repository svishniakov/agent-flow (21 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 730 once invoked, about $0.0001 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
Build Next.js applications with React components, shadcn/ui, and Tailwind CSS. Expert in SSR/SSG, app router, and modern frontend patterns. Use PROACTIVELY for Next.js development, UI component creation, or frontend architecture.
Frontend
React/Next.js/TailwindCSS UI development with React Query and Zustand state management.
frontend-ui-component-agent
/ui-component-agent or @ui-component-agent.
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
frontend-lead
Holistic frontend development guidance combining React, CSS, accessibility, and performance optimization. Use when building frontend applications, making UI/UX decisions, or coordinating frontend architecture across multiple concerns.
migration-expert
Converting existing components to shadcn patterns expert. Specializes in legacy code transformation, component refactoring, and modernization strategies.