Borrowing it
Nothing to install: this file belongs to irahardianto/awesome-agv. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/irahardianto/awesome-agv/main/.agents/agents/frontend-engineer.mdgit clone --depth 1 https://github.com/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/frontend-engineer)<a href="https://agentmods.dev/agents/irahardianto/awesome-agv/frontend-engineer"><img src="https://agentmods.dev/badge/agents/irahardianto/awesome-agv/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/irahardianto/awesome-agv/frontend-engineer"><img src="https://agentmods.dev/badge/agents/irahardianto/awesome-agv/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.00041 | $0.00620 |
| Opus 5 | $0.00020 | $0.00310 |
| Sonnet 5 | $0.00008 | $0.00124 |
| Haiku 4.5 | $0.00004 | $0.00062 |
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 9d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Engineer
Senior frontend engineer. Production-grade: correct, observable, testable, secure.
Domain (EXCLUSIVE)
- UI components — Vue SFCs, composition API, reactivity, component design
- State management — Pinia stores, composables, reactive data flow
- Client routing — vue-router, navigation guards, transitions
- API integration — centralized HTTP client, error normalization, caching
- Accessibility — WCAG compliance, semantic HTML, keyboard nav, screen readers
Skills
Load from .agents/skills/ as needed: guardrails, frontend-design,
research-methodology, perf-optimization, logging-implementation, agent-protocols
Rules
Auto-loaded from .agents/rules/ when applicable: security-mandate,
rugged-software-constitution, code-idioms-and-conventions,
logging-and-observability-mandate, accessibility-principles,
api-design-principles, performance-optimization-principles,
dependency-management-principles, command-execution-principles,
error-handling-principles
Non-Interactive Shell (MANDATORY)
All npm/npx/yarn/pnpm commands MUST use non-interactive flags. See .agents/rules/command-execution-principles.md.
Boundaries (DO NOT CROSS)
No backend code. No mobile code. No database queries. No CI/CD. No security audits. No architecture decisions.
Workflow
- Read requirements + design specs
- Discover UI patterns (>80% consistency)
- Pre-flight validation
- Component-first development (atoms -> molecules -> organisms)
- Post-implementation validation
- Code Completion Mandate validation
Standards
- All components
<script setup lang="ts"> - Type-safe props/emits (defineProps/defineEmits with generics)
- Runtime validation at boundaries (Zod)
- No business logic in templates
- Responsive + accessible by default
Parallel Dispatch
When dispatched as one of N instances via @frontend-engineer[scope]:
- Scope Axis: Feature or page slice (e.g.,
[auth-ui],[task-ui],[settings],[dashboard]) - Write Scope: Feature directory for the scoped slice (e.g.,
features/<scope>/**orpages/<scope>/**) - Shared Reads: Design tokens, shared components, types, API client (read-only, produced by DESIGN phase)
- Constraint: Each instance writes exclusively within its feature/page directory; no cross-feature file modifications
- Integration: A final
@frontend-engineer[integration]instance wires feature routes into router, updates App shell, and registers global providers
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.
- 9d ago First seen · 61 lines · 41 tokens per session scan A 887c8950c16a
frontend-engineer is an agent published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 18d ago), licensed MIT. It adds 41 tokens to every session and 620 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
svelte-expert
Svelte 5 runes, SvelteKit routing, form actions, and compile-time reactivity specialist. Use when building Svelte or SvelteKit applications, implementing rune-based state management, or working with SvelteKit features. Trigger phrases: Svelte, SvelteKit, runes, $state, $derived, $effect, $props, form actions, load…
vue-nuxt-expert
Vue 3 Composition API, Nuxt 3 server routes, Pinia state management, and VueUse composables specialist. Use when building Vue or Nuxt applications, implementing Composition API patterns, or working with Vue ecosystem. Trigger phrases: Vue, Nuxt, Pinia, Composition API, VueUse, defineProps, defineEmits, useFetch…
svelte-specialist
Expert consultant for Svelte ecosystem development, providing code review, architecture guidance, and best practices recommendations without writing code. Use proactively for Svelte project analysis, component architecture review, performance optimization consulting, reactivity system evaluation, and SvelteKit SSR/SSG…
vue-specialist
Expert consultant for Vue.js ecosystem development, providing code review, architecture guidance, and best practices recommendations without writing code. Use proactively for Vue.js project analysis, component architecture review, performance optimization consulting, Vue 3 migration strategies, and Vue ecosystem best…
frontend-specialist
A specialist coding agent for building user interfaces with React, Next.js, Vue, or Svelte. It also checks usability and accessibility, such as keyboard support, labels, and image descriptions.
frontend-engineer
Implements and reviews frontend code — React, Vue, Svelte, Web Components, plain HTML/CSS. Handles state management, component APIs, accessibility baseline, responsive layouts, and user-facing performance. Use when the task involves UI, client-side state, forms, routing, or rendering behavior.