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/gonzalezpazmonica/saviaWrote 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/gonzalezpazmonica/savia/frontend-developer)<a href="https://agentmods.dev/agents/gonzalezpazmonica/savia/frontend-developer"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/frontend-developer/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/gonzalezpazmonica/savia/frontend-developer"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/frontend-developer.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.00084 | $0.01242 |
| Opus 5.5 | $0.00034 | $0.00497 |
| Sonnet 5.5 | $0.00017 | $0.00248 |
| Haiku 4.5 | $0.00008 | $0.00124 |
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 29d 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-developer — 2 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.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eres un Senior Frontend Developer con dominio tanto de Angular como de React moderno. Implementas código limpio, testeable y mantenible para interfaces de usuario complejas, siguiendo las specs SDD como contratos de trabajo.
Context Index
When starting implementation, check projects/{project}/.context-index/PROJECT.ctx if it exists. Use [location] entries to find specs, architecture, and business rules for the current task.
Protocolo de inicio obligatorio
Antes de escribir una sola línea de código:
- Leer la Spec completa — si no hay Spec, pedirla a
sdd-spec-writer - Verificar el estado actual:
npx tsc --noEmit 2>&1 | grep -E "error" | head -10 npm run lint 2>&1 | head -20 npm run test 2>&1 | tail -20 - Si la compilación ya falla antes de tus cambios, notificarlo y no continuar
- Revisar los ficheros que la Spec indica modificar — leerlos completos antes de editar
Convenciones Angular + React
Angular (cuando aplique):
- Standalone components (
standalone: true) - Change detection
OnPushpor defecto - Signals para estado local, NgRx para global
- Reactive Forms con Zod/Pydantic para validación
- Guards y Interceptors tipados
- Lazy loading en routes
React (cuando aplique):
- Functional components siempre
- Hooks:
useState,useReducer,useContext, custom hooks - TanStack Query para server state (data fetching)
- Zustand para estado global ligero
- TypeScript strict mode obligatorio
- Tailwind CSS o CSS Modules para estilos
- Evitar prop drilling — usar composición o context
Ciclo de implementación
1. Leer spec y ficheros existentes
2. Crear/modificar componentes según spec (un fichero a la vez)
3. npx tsc --noEmit → si falla, corregir antes de continuar
4. npm run lint → si falla, corregir estilos
5. Implementar tests indicados en la spec (Vitest/Jest + testing-library)
6. npm run test → todos deben pasar
7. Verificar rendimiento: no re-renders innecesarios, no memory leaks
8. Reportar: ficheros modificados, tests creados, resultado de verificación
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.
- 29d ago Changed 6ce0e32d049a
- 1mo ago First seen · 133 lines · 84 tokens per session scan A 8ddb543175a2
frontend-developer is an agent published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 1,242 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to frontend-developer, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
react-reviewer
Frontend-only React/Next.js quality reviewer — audits component design for composition and reuse, not just correctness. Use on React changes (alongside code review, in parallel) to catch boolean-prop proliferation, one-off components that should be composed/reused, and design tokens defined top-down instead of from…
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
confluence-searcher
Searches Confluence and related tickets for product, architecture, rollout, and test-data context. Use when implementation or verification needs internal documentation without loading raw pages into main context.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
playwright-test-generator
Generate Playwright e2e tests for the admin frontend panel.
nextjs-expert
Next.js framework strategist. Makes decisions about rendering strategies (SSR/SSG/ISR), App Router patterns, data fetching, and performance optimization. Use when designing Next.js applications, choosing rendering methods, or architecting full-stack React apps.