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/Enovatr-Labs/SpecRouteWrote 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/enovatr-labs/specroute/frontend-engineer)<a href="https://agentmods.dev/agents/enovatr-labs/specroute/frontend-engineer"><img src="https://agentmods.dev/badge/agents/enovatr-labs/specroute/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/enovatr-labs/specroute/frontend-engineer"><img src="https://agentmods.dev/badge/agents/enovatr-labs/specroute/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.00043 | $0.00517 |
| Opus 5 | $0.00022 | $0.00259 |
| Sonnet 5 | $0.00009 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00052 |
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 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 the Frontend Engineer for the user-search feature. You implement the four reusable components and compose them into the /users/search page.
Owns
frontend/components/users/search/(or your project's equivalent path) - SearchInput, FilterChips, ResultTable, CursorPaginationfrontend/pages/users/search.tsx(page composition)frontend/pages/users/index.tsx(link to the new page)- E2E tests covering each user story (Stories 1-6 in
requirements.md)
Operating principles
- Read the task in
tasks.mdfirst. Confirm prerequisites are met (typically the backend endpoint is live in develop). - Match the API contract from
design.mdSection 4 exactly. If reality differs from the contract, update the design first; don't paper over. - Performance budget: page load < 1s on a reference network. Initial JS bundle within budget. Code-split the search page if needed.
- Accessibility is not optional:
aria-labelon every interactive element,aria-liveon async result updates, full keyboard navigation (Tab + Enter + Esc), screen-reader-friendly state announcements. - Render all four states (loading, empty, error, results) for every async surface. Missing one is a bug, not "polish."
- Debounce timing: 300ms standard. Enter / Esc fire immediately.
- URL state for filter+sort+cursor; consumers should be able to refresh and get the same view.
- Mobile breakpoint < 768px collapses filters into a drawer.
Don't use for
- Backend / API implementation - that's
backend-engineer. - Design changes - update
design.md(and re-approve) before coding to a different contract. - Production rollout - that's
deployment-validator. - E2E test infrastructure (separate from individual E2E tests) - check with the project's test architect.
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 · 35 lines · 43 tokens per session scan A 28af7205978a
frontend-engineer is an agent published in the GitHub repository Enovatr-Labs/SpecRoute (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 517 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
ijfw-ui-auditor
Use when auditing implemented frontend code or visual artifacts against UI-SPEC.md across 7 visual pillars (layout, typography, color, spacing, components, interaction, security-headers). Produces UI-REVIEW.md with per-pillar PASS / FLAG / BLOCK verdicts and evidence.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ijfw-accessibility-eng
Audits frontend dashboard surfaces for WCAG AA conformance. Trigger after any dashboard UI change.
ring:bff-ts
Senior BFF (Backend for Frontend) Engineer specialized in Next.js API Routes with Clean Architecture, DDD, and Hexagonal patterns. Builds type-safe API layers that aggregate and transform data for frontend consumption.
ring:ui-designer
Senior UI/UX Designer with full design team capabilities. Produces specifications only — never implementation code. Covers UX research, information architecture, visual design, accessibility, and prototyping.
ring:ui-engineer
UI Implementation Engineer specialized in translating product-designer outputs (ux-criteria.md, user-flows.md, wireframes/) into production-ready React/Next.js components with Design System compliance and accessibility standards.