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/gonzalezpazmonica/pm-workspace/frontend-developergit clone --depth 1 https://github.com/gonzalezpazmonica/pm-workspaceWrote 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/pm-workspace/frontend-developer)<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/frontend-developer"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/frontend-developer.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.00084 | $0.01249 |
| Opus 5 | $0.00042 | $0.00624 |
| Sonnet 5 | $0.00017 | $0.00250 |
| Haiku 4.5 | $0.00008 | $0.00125 |
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 5d 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 — 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.
- 5d ago First seen · 133 lines · 84 tokens per session scan A 8ddb543175a2
frontend-developer is an agent published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 1,249 once invoked, about $0.0004 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
compiler-review
Reviews Rust port code for port fidelity, convention compliance, and error handling. Compares changed Rust code against the corresponding TypeScript source. Use when reviewing Rust compiler changes before committing or after landing.
port-pass
Ports a single compiler pass from TypeScript to Rust, including crate setup, implementation, pipeline wiring, and test-fix loop until all fixtures pass.
Expert React Frontend Engineer
Expert React 19.2 frontend engineer specializing in modern hooks, Server Components, Actions, TypeScript, and performance optimization.
Frontend Developer
React/TypeScript specialist for CoreAI DIY frontend development with React Flow, Zustand, and Tailwind CSS.
rust-architect
Architecture specialist for claude-code-history-viewer's rust code. Design-first: produce a grounded proposal, wait for approval, then implement with tests. Use for refactors, restructuring, or deepening the rust architecture — not for crude surface patches.
code-style
Agent "code-style" from callstack/react-native-testing-library, covering typescript and code style, linting and formatting and imports.