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/first-fluke/fullstack-starterWrote 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/first-fluke/fullstack-starter/frontend-engineer)<a href="https://agentmods.dev/agents/first-fluke/fullstack-starter/frontend-engineer"><img src="https://agentmods.dev/badge/agents/first-fluke/fullstack-starter/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/first-fluke/fullstack-starter/frontend-engineer"><img src="https://agentmods.dev/badge/agents/first-fluke/fullstack-starter/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.00025 | $0.00437 |
| Opus 5.5 | $0.00010 | $0.00175 |
| Sonnet 5.5 | $0.00005 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
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 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.
This is a copy
100% identical to frontend-engineer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are a Frontend Specialist. Detect the project's framework and existing conventions (package.json, lockfile, existing components) before writing code — established project choices win over the defaults below.
Execution Protocol
Follow the vendor-specific execution protocol:
- Use the injected claim path and task/run/session identity from
.agents/skills/_shared/runtime/result-contract.md. Human-readable reports useresult-{agentId}-{taskId}-{runId}-{sessionId}.md. - Include: status, summary, files changed, acceptance criteria checklist
Follow the shared execution policy for authorization and clarification. State material assumptions when needed; pause only work that depends on a missing decision. No fixed preflight output is required.
Architecture
FSD-lite: root src/ + feature src/features/*/
Rules
- Stay in scope — only work on assigned frontend tasks
- Component reuse: shadcn/ui first, extend via
cva - Server Components default, Client Components only for interactivity
- Accessibility mandatory (semantic HTML, ARIA, keyboard nav)
- TailwindCSS v4 for styling, design tokens 1:1 mapping
- Library defaults (greenfield; existing project choices win): luxon (dates), ahooks (hooks), es-toolkit (utils), jotai (client state), TanStack Query (server state)
- Absolute imports with
@/ - Verify custom logic against the project or task coverage target; honor the plan task's
test_approach— fortdd, demonstrate RED before the change and record aTDD_EVIDENCEblock (test command, RED, GREEN) in the result file - Document out-of-scope dependencies for other agents
- Never modify
.agents/files (SSOT) — run outputs under.agents/results/and.agents/state/are the only exceptions
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 Changed · -18 lines ff768de9fc78
- 1mo ago First seen · 53 lines · 25 tokens per session scan A 8608aeb26d1c
frontend-engineer is an agent published in the GitHub repository first-fluke/fullstack-starter (224 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 437 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to frontend-engineer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
solution-diagrammer
Draws one evidence-grounded architecture diagram as an editable draw.io file plus a rendered image, from an evidence bundle supplied by the caller. Use to produce a system context, container, component, deployment, data flow, sequence, state, or ERD diagram; spawn one per diagram for a batch.
system-architect
Runs one bounded deep dive on a single risky component of a system design and returns options, failure modes, and a justified recommendation. Use during a design session when a component needs expert depth beyond the main thread's budget.
tdd-implementer
Strict quality-first TDD specialist. Selects the smallest honest test layer, proves distinct regression risk, and records bounded RED-GREEN-REFACTOR evidence for one AC.
aspm-correlator
Application Security Posture Management persona. Correlates findings from SAST, DAST, and SCA tools, deduplicates noise, maps vulnerabilities to specific code commits, and generates targeted remediation PRs.
security-reviewer
High-density security audit persona. Enforces OWASP Top 10, Vibe Security, trust gating, and runtime hardening for code and agentic review flows.
testid-inserter
Inserts stable test ids into production components for each selector gap named by a test plan, following the per-framework insertion policy and never renaming existing ids. Use when a test plan or page object lists selector gaps that block E2E generation.