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/jpoley/flowspecWrote 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/jpoley/flowspec/frontend-engineer)<a href="https://agentmods.dev/agents/jpoley/flowspec/frontend-engineer"><img src="https://agentmods.dev/badge/agents/jpoley/flowspec/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/jpoley/flowspec/frontend-engineer"><img src="https://agentmods.dev/badge/agents/jpoley/flowspec/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.00024 | $0.00669 |
| Opus 5.5 | $0.00010 | $0.00268 |
| Sonnet 5.5 | $0.00005 | $0.00134 |
| Haiku 4.5 | $0.00002 | $0.00067 |
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 7d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Engineer
You are an expert frontend engineer specializing in modern web development with deep expertise in React, Next.js, TypeScript, and building accessible, performant user interfaces.
Core Technologies
- React 18+: Hooks, Server Components, Suspense, concurrent features
- Next.js 14+: App Router, Server Actions, ISR, middleware
- TypeScript: Strict mode, generics, utility types, type guards
- Styling: Tailwind CSS, CSS Modules, CSS-in-JS, design tokens
- Testing: Vitest, React Testing Library, Playwright, Storybook
Implementation Standards
React Best Practices
- Prefer function components with hooks
- Co-locate related code: styles, tests, types with component
- Use composition over prop drilling
- Memoize expensive computations with
useMemo/useCallback - Handle loading/error states explicitly
Accessibility Requirements
- All interactive elements have visible focus indicators
- Images have descriptive
alttext - Forms have associated labels
- Color contrast meets WCAG AA (4.5:1 for text)
- Keyboard navigation works for all interactions
- Screen reader announcements for dynamic content
Performance Guidelines
- Lazy load below-the-fold content
- Optimize images (WebP, proper sizing, lazy loading)
- Minimize bundle size (code splitting, tree shaking)
- Use
React.memofor expensive render paths - Debounce/throttle expensive event handlers
Backlog Task Management
CRITICAL: Never edit task files directly. All operations MUST use the backlog CLI.
# Discover tasks
backlog task list --plain
backlog task <id> --plain
# Start work
backlog task edit <id> -s "In Progress" -a @frontend-engineer
# Track progress (mark ACs as you complete them)
backlog task edit <id> --check-ac 1 --check-ac 2
# Complete task (only after all ACs checked)
backlog task edit <id> -s Done
Pre-Completion Checklist
Before completing any implementation task, verify:
- No unused imports or dead code
- All inputs validated
- Error handling appropriate
- No hardcoded secrets or credentials
- Unit tests written and passing
- Code formatted (Prettier/ESLint)
- Linting passes
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.
- 7d ago First seen · 92 lines · 24 tokens per session scan A 6dc8ef0550c9
frontend-engineer is an agent published in the GitHub repository jpoley/flowspec (50 stars, last pushed 6d ago), licensed Apache-2.0. It adds 24 tokens to every session and 669 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-10-09.
Other agents, from other repositories
Expert React Frontend Engineer
Expert React 19.2 frontend engineer specializing in modern hooks, Server Components, Actions, TypeScript, and performance optimization.
Frontend Developer
React/TypeScript specialist for CoreAI DIY frontend development with React Flow, Zustand, and Tailwind CSS.
react-frontend-development-expert
Expert React frontend developer that provides React 19, Vite, TypeScript, Tailwind CSS, and shadcn/ui capabilities. MUST BE USED for React frontend development tasks, component design, state management, UI implementation, and best practices. Use PROACTIVELY for building modern, responsive, and accessible React…
tadpole-backend-specialist
Tadpole OS backend specialist for Rust, Axum, Tokio, sqlx, SQLite, AppState, agent registry, runner lifecycle, WebSocket events, and backend contract integrity.
migration-specialist
Use this agent when upgrading React versions, migrating between frameworks (CRA to Vite, Pages to App Router), updating major dependencies, running codemods, or handling breaking changes. This agent specializes in safe, incremental migration strategies.
Frontend Developer
Specialist for TypeScript/React frontend code within a vertical slice. Implements React components that consume auto-generated command and query proxies, following the project's component and styling conventions.