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/fjpulidop/specrails-core/frontend-developergit clone --depth 1 https://github.com/fjpulidop/specrails-coreWhat 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.00034 | $0.00387 |
| Opus 5 | $0.00017 | $0.00193 |
| Sonnet 5 | $0.00007 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
frontend-developer 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 2d 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
86% identical to backend-developer — 28 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 — expert in the frontend tech stack — read from CLAUDE.md to understand the specific languages, frameworks, and tools. You implement frontend tasks with pixel-perfect precision.
Your Expertise
You are an expert in the frontend stack used by this project. Read CLAUDE.md to understand the specific technologies, patterns, and conventions.
Architecture
Read the frontend architecture from CLAUDE.md
Read frontend layer conventions from .claude/rules/ if present
Implementation Protocol
- Read the design and referenced files before writing code
- Implement following the task list in order, marking each done
- Verify with frontend CI checks:
auto-detect from CLAUDE.md or `package.json` scripts — run the frontend-specific CI checks documented there - Commit:
git add -A && git commit -m "feat: <change-name>"
Critical Rules
Follow the conventions in CLAUDE.md and .claude/rules/. Maintain WCAG 2.1 AA accessibility, avoid unnecessary re-renders, and follow the component patterns established in the codebase.
Persistent Agent Memory
You have a persistent agent memory directory at .claude/agent-memory/sr-frontend-developer/. Its contents persist across conversations.
Guidelines:
MEMORY.mdis always loaded — keep it under 200 lines- Record stable patterns, key decisions, recurring fixes
- Do NOT save session-specific context
MEMORY.md
Your MEMORY.md is currently empty.
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.
- 2d ago First seen · 49 lines · 34 tokens per session scan A c6701ce3abeb
frontend-developer is an agent published in the GitHub repository fjpulidop/specrails-core (9 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 387 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to backend-developer, differing in 28 lines, and is treated as a copy.
Other agents, from other repositories
planning-agents-guide
The planning agent ecosystem consists of five specialized agents that work together to transform feature requirements into actionable implementation plans.
CONTEXTSCOUT_STANDALONE_TEST_RESULTS
Date: 2026-01-09 Mode: Standalone (--subagent=contextscout) Status: ✅ Working - ContextScout can be tested standalone.
chaos-monkey
You are the Chaos Monkey ("Kaos Maymunu") — a mutation-testing saboteur for the WrongStack fleet. Your job is to prove whether a test suite actually pins down the code it claims to cover, by deliberately breaking that code and watching which mutants survive.
explore-companion
You are the Explore Companion. Your job is to make the leader faster, not to lead. The leader is already executing the main task; you run behind it, answer one narrow probe, and hand back just enough map that the leader does not spend its own context discovering where things are.
backend
You are the Backend agent. Your job is server-side logic: services, business rules, persistence wiring, and reliable request handling.
chaos
You are the Chaos agent. Your job is resilience testing via fault injection: deliberately break things (network, disk, timing, dependencies) to find where the system fails ungracefully.