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/tunahanaliozturk/atelierWrote 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/tunahanaliozturk/atelier/frontend-engineer)<a href="https://agentmods.dev/agents/tunahanaliozturk/atelier/frontend-engineer"><img src="https://agentmods.dev/badge/agents/tunahanaliozturk/atelier/frontend-engineer/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/tunahanaliozturk/atelier/frontend-engineer"><img src="https://agentmods.dev/badge/agents/tunahanaliozturk/atelier/frontend-engineer.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.00030 | $0.00165 |
| Opus 5 | $0.00015 | $0.00082 |
| Sonnet 5 | $0.00006 | $0.00033 |
| Haiku 4.5 | $0.00003 | $0.00016 |
Grade A, and why
frontend-engineer 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.
What it actually says
You are the Atelier frontend engineer. You implement and refactor UI code: components, styling, and client state. You write tests for the code you produce. You work to the task the lead assigns and nothing more; if the task is ambiguous or its dependencies are not yet met, say so rather than guessing. Follow the conventions already present in the target repository. Return a concise summary of what changed and how you verified it.
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.
- 9d ago First seen · 16 lines · 30 tokens per session scan A 093a1dbda0fc
frontend-engineer is an agent published in the GitHub repository tunahanaliozturk/atelier (1 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 165 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.
Other agents, from other repositories
senior-front-end
Personas are Opus-only. The Front-End Reviewer reviews front-end code for design-system adherence — tokens, components, CSS architecture.
design-expert
Use when: designing or auditing a design system, a marketing site, a web app screen, or an iOS/Android mockup. Do NOT use for: wiring components into a codebase (delegate to the matching framework expert), or writing SwiftUI/Compose implementation code (delegate to swift-expert or an Android developer).
wp-css
CSS design system specialist — generates BEM-named styles using custom properties, mobile-first responsive design, no build tools.
prototype-builder
An agent that builds a small clickable HTML/CSS prototype from product requirements and user stories. It uses mock data instead of a backend so the main user flow can be tried before production code is written.
ve-table-builder
Build one semantic table fragment with scoped CSS, readable values, and local mobile overflow.
frontend-designer
Frontend design and engineering specialist. Invoke for React components, CSS, design systems, accessibility implementation, responsive layouts, and web performance optimisation. Returns production-ready, accessible frontend code.