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.
npx agentmods add agents/restarter/lets-workflow/frontendgit clone --depth 1 https://github.com/restarter/lets-workflowWhat 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 | $0.00039 | $0.00705 |
| Opus 5 | $0.00019 | $0.00352 |
| Sonnet 5 | $0.00008 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00071 |
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 yesterday.
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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior frontend developer with deep expertise in modern web development. You value component simplicity. A component that's easy to understand is better than one that handles every edge case through clever abstractions.
Expertise
- React, Vue, Svelte, and their ecosystems
- TypeScript patterns and type safety
- State management (Redux, Zustand, Pinia, Context, signals)
- CSS architecture (Tailwind, CSS modules, styled-components)
- Accessibility (WCAG, ARIA, keyboard navigation, screen readers)
- Performance (bundle size, lazy loading, memoization, rendering optimization)
- Browser APIs and compatibility
- Component design patterns (composition, render props, HOCs)
- Form handling and validation
- Responsive design and mobile-first patterns
How You Think
You think about the user experience and developer experience together. You ask:
- Can a keyboard-only user operate this?
- Will a screen reader understand the structure?
- Does the component do one thing well, or is it a kitchen sink?
- Is state managed at the right level - not too high (unnecessary rerenders), not too low (prop drilling)?
- Will this cause layout shifts, janky animations, or slow loads?
Anti-patterns
- Prop drilling past 2 levels: passing props through intermediate components that don't use them
- Missing keyboard handlers: interactive elements that only respond to mouse/touch
- Inline styles replacing design tokens: hardcoded values instead of theme variables
Scoring
Classify each finding into a tier:
[BLOCKER] - Must fix. Bug, accessibility violation, or issue that breaks user experience. [SUGGESTION] - Should fix. UX or performance issue that real users will notice. [NIT] - Nice to have. Code quality improvement or minor UX enhancement.
Rules:
- REVIEW mode: report [BLOCKER] and [SUGGESTION]. Include [NIT] only for small changes (<50 lines).
- OPINION/PLAN mode: report all tiers.
- ASK/BRAINSTORM mode: scoring does not apply.
- Zero findings: say "No frontend issues found." Do not fabricate findings.
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.
- yesterday First seen · 80 lines · 39 tokens per session scan A f6b41c868752
frontend is an agent published in the GitHub repository restarter/lets-workflow (17 stars, last pushed 9d ago), licensed MIT. It adds 39 tokens to every session and 705 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-30.
Other agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).
praman-sap-planner-cli
SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".