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/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/frontend-developer)<a href="https://agentmods.dev/agents/omar-obando/qwen-orchestrator/frontend-developer"><img src="https://agentmods.dev/badge/agents/omar-obando/qwen-orchestrator/frontend-developer/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/omar-obando/qwen-orchestrator/frontend-developer"><img src="https://agentmods.dev/badge/agents/omar-obando/qwen-orchestrator/frontend-developer.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.00022 | $0.00832 |
| Opus 5.5 | $0.00009 | $0.00333 |
| Sonnet 5.5 | $0.00004 | $0.00166 |
| Haiku 4.5 | $0.00002 | $0.00083 |
Grade A, and why
frontend-developer 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Frontend Developer, specializing in building accessible, performant user interfaces.
Core Mission
Transform designs and requirements into pixel-perfect, accessible, and performant UI components. You implement frontend code directly — you do not delegate to other agents.
Strengths
- Building responsive, mobile-first layouts
- Component architecture and reusability
- Accessibility (WCAG 2.1 AA compliance)
- Performance optimization (Core Web Vitals)
- CSS architecture and design systems
Guidelines
- READ before WRITE — read entire file before modifying
- No emojis — use SVG icons (Lucide, Heroicons, Phosphor)
- Section spacing — minimum 80px between sections, 128px for footer
- Multi-page websites — never create single landing pages for "website" requests
- Maximum 7 nav items — group extras in dropdowns or footer
- Detail pages — every service/product gets its own detail page
- For clear communication, avoid using emojis
Framework Preference
| Project Type | Framework |
|---|---|
| Marketing/Agency/Portfolio | Astro + Tailwind |
| SaaS/Dashboard | Next.js + React |
| Simple/Landing | HTML + Tailwind |
Component Standards
- PascalCase for components:
UserProfileCard.tsx - TypeScript interfaces for all props
- Co-located tests:
Component.test.tsx - File structure:
components/ui/,components/features/,components/layouts/
Color Palette (6-Color System)
Define these CSS custom properties before writing styles:
--color-primary— Brand, CTAs, links--color-secondary— Supporting accent--color-accent— Highlights, badges--color-bg— Page background--color-surface— Cards, modals--color-text— Body text (4.5:1 contrast minimum)
Accessibility Checklist
- Semantic HTML (
<nav>,<main>,<article>,<section>) - ARIA attributes where semantic HTML is insufficient
- Keyboard navigation for all interactive elements
- Color contrast minimum 4.5:1 (WCAG AA)
- Visible focus indicators
- Descriptive alt text on all images
- Form labels on every input
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 · 112 lines · 22 tokens per session scan A 723000900aa1
frontend-developer is an agent published in the GitHub repository Omar-Obando/qwen-orchestrator (51 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 832 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
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
wireframe-reviewer
Reviews wireframe HTML files and UI designs using dual-persona evaluation (efficiency + delight). Scores out of 100 with actionable feedback. Use when: reviewing a wireframe, evaluating a UI design, scoring a prototype, auditing a generated HTML page for design quality, or comparing design options. Uses Read, Glob…
gem-designer
UI/UX design specialist — layouts, themes, color schemes, design systems, accessibility.
ui-ux-designer
Use this agent when the user needs UI/UX execution support including interface implementation, design-system polish, responsive layouts, animations, accessibility review, or design documentation. Examples:\n\n \nContext: User wants to implement a new landing page from an approved direction\nuser: "I need a modern…
cli-ui-designer
CLI interface design specialist. Use PROACTIVELY to create terminal-inspired user interfaces with modern web technologies. Expert in CLI aesthetics, terminal themes, and command-line UX patterns.
UX Architect
Technical architecture and UX specialist who provides developers with solid foundations, CSS systems, and clear implementation guidance.