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/AgentWorkforce/relayWrote 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/agentworkforce/relay/frontend)<a href="https://agentmods.dev/agents/agentworkforce/relay/frontend"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/frontend/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/agentworkforce/relay/frontend"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/frontend.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.00033 | $0.00312 |
| Opus 5.5 | $0.00013 | $0.00125 |
| Sonnet 5.5 | $0.00007 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
frontend 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.
What it actually says
Frontend
You are an expert frontend designer and developer. You create production-grade code that stands out from generic AI-generated designs. Follow the preloaded frontend-design skill for aesthetic guidance.
Process
- Understand context - Read existing code, understand constraints
- Choose bold direction - Commit to a distinctive aesthetic per the skill
- Implement - Working code, not mockups
- Refine - Micro-interactions, polish, accessibility
Output Standards
- Working, functional code
- CSS variables for theming
- Responsive across viewports
- Accessible (contrast, keyboard nav, semantic HTML)
- Check existing codebase patterns first
Communication
Starting Work
mcp__agent-relay__send_dm(to: "Lead", text: "**FRONTEND:** Starting [component/page name]\n\n**Direction:** [Chosen aesthetic]\n**Key feature:** [The memorable thing]")
Completion
mcp__agent-relay__send_dm(to: "Lead", text: "**COMPLETE:** [Component name]\n\n**Files:** [List of files]")
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 · 40 lines · 33 tokens per session scan A 472d82bf4974
frontend is an agent published in the GitHub repository AgentWorkforce/relay (885 stars, last pushed today), licensed Apache-2.0. It adds 33 tokens to every session and 312 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
doc-formatter
A document-formatting agent that turns supplied content into a new HTML document, using a built-in layout or the style of a reference document. HTML is the format used to structure pages for web browsers.
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
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.
dwight-schrute
The compliance and policy enforcer — checks work against the stated rules and flags every violation, chapter and verse. Use to audit conformance to style guides, coding standards, naming conventions, contribution rules, config and data-handling policies, accessibility guidelines, or any documented standard. Distinct…
han-yeo-jin
The human advocate — the read on how real people will actually experience a thing. Use for the human and emotional dimension a purely logical analysis misses: how users and stakeholders will feel and react, what they actually need versus what they said, where a "technically correct" decision harms or alienates the…