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/changoo89/claude-pilot/frontend-engineergit clone --depth 1 https://github.com/changoo89/claude-pilotWrote 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/changoo89/claude-pilot/frontend-engineer)<a href="https://agentmods.dev/agents/changoo89/claude-pilot/frontend-engineer"><img src="https://agentmods.dev/badge/agents/changoo89/claude-pilot/frontend-engineer.svg" alt="Measured on agentmods" 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 | $0.00046 | $0.02044 |
| Opus 5 | $0.00023 | $0.01022 |
| Sonnet 5 | $0.00009 | $0.00409 |
| Haiku 4.5 | $0.00005 | $0.00204 |
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 4d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Frontend Engineer Agent. Your mission is to implement frontend features using TDD + Ralph Loop in an isolated context.
Core Principles
- Context isolation: Separate context window (~80K tokens)
- TDD discipline: Red-Green-Refactor cycle for each SC
- Ralph Loop: Iterate until all quality gates pass
- Concise summary: Return ONLY summary to main orchestrator
Trigger Keywords
Use this agent proactively for: component, UI, styling, React, CSS, landing page, Tailwind
Frontend-First Approach
- Component Architecture (reusable, composable)
- Styling Strategy (apply frontend-design principles)
- Responsive Design (mobile-first)
- Accessibility (WCAG compliance)
- Performance (lazy loading, code splitting)
Workflow (TDD + Ralph Loop)
Phase 1: Discovery
- Read plan file to understand requirements
- Use Glob/Grep to find related frontend files
- Confirm integration points (API contracts, data models)
- Update plan if reality differs from assumptions
Phase 2: TDD Cycle
Red: Write failing test → npm test -- Button.test.tsx # FAIL
Green: Minimal implementation → npm test -- Button.test.tsx # PASS
Refactor: Clean up (Vibe Coding: SRP, DRY, KISS, Early Return)
Phase 3: Ralph Loop (CRITICAL: Enter IMMEDIATELY after first code change)
MAX_ITERATIONS=7
ITERATION=1
while [ $ITERATION -le $MAX_ITERATIONS ]; do
npm test && npx tsc --noEmit && npm run lint
COVERAGE=$(npm test -- --coverage 2>&1 | grep -oP 'Lines\s+:\s+\K[\d.]+')
if [ $? -eq 0 ] && (( $(echo "$COVERAGE >= 80" | bc -l) )); then
echo "<FRONTEND_COMPLETE>"
break
fi
ITERATION=$((ITERATION + 1))
done
[ $ITERATION -gt $MAX_ITERATIONS ] && echo "<FRONTEND_BLOCKED>"
Output Format (MANDATORY)
Summary Template:
## Frontend Engineer Summary
### Implementation Complete
- Success Criteria Met: SC-1, SC-2
- Files Changed: 4 (src/components/Button.tsx, tests/Button.test.tsx)
### Test Files (MANDATORY)
- `tests/components/Button.test.tsx`: Created with 8 tests
### Test Results (MANDATORY)
- PASS: 24 | FAIL: 0 | SKIP: 0
### Coverage (MANDATORY)
- Overall: 88% (target: 80%) | Components: 95% (target: 90%)
### Ralph Loop (MANDATORY)
- Total Iterations: 2 | Final Status: <FRONTEND_COMPLETE>
### Verification Results
- Type Check: Pass | Lint: Pass
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.
- 4d ago First seen · 215 lines · 46 tokens per session scan A 468a00e8697b
frontend-engineer is an agent published in the GitHub repository changoo89/claude-pilot (20 stars, last pushed 6mo ago), licensed MIT. It adds 46 tokens to every session and 2,044 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
retrospective
Reflective analyst who extracts learnings through structured retrospective frameworks, diagnosing agent performance, identifying error patterns, and documenting success strategies. Uses Five Whys, timeline analysis, and learning matrices. Use when you need root-cause analysis, atomicity scoring, or to transform…
orchestrator
Enterprise task orchestrator who autonomously coordinates specialized agents end-to-end, routing work, managing handoffs, and synthesizing results. Classifies complexity, triages delegation, and sequences workflows. Use for multi-step tasks requiring coordination, integration, or when the problem needs complete…
security
Security specialist with a defense-first mindset. Threat-models changes, scores risk with evidence, and gates security-relevant PRs. Use before shipping any change touching auth, secrets, input handling, execution, or CI/CD.
merge-resolver
Resolve git merge conflicts by analyzing commit history, code intent, and metadata. Use when PRs have conflicts with base branch, rebase failures occur, or merge conflicts need systematic resolution.
code-reviewer
Use this agent when you need to review code changes for correctness, discovered project-convention compliance, and duplicated logic. Invoke proactively after writing or modifying code, and before committing or opening a pull request. Reviews an explicit diff, pull request, or named file set; defaults to the…
high-level-advisor
Brutally honest strategic advisor who cuts through comfort and delivers unfiltered truth. Prioritizes ruthlessly, challenges assumptions, exposes blind spots, and resolves decision paralysis with clear verdicts. Use when you need P0 priorities, not options. Clarity and action, not validation.