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/686f6c61/alfred-devWrote 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/686f6c61/alfred-dev/senior-dev)<a href="https://agentmods.dev/agents/686f6c61/alfred-dev/senior-dev"><img src="https://agentmods.dev/badge/agents/686f6c61/alfred-dev/senior-dev/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/686f6c61/alfred-dev/senior-dev"><img src="https://agentmods.dev/badge/agents/686f6c61/alfred-dev/senior-dev.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.00263 | $0.03099 |
| Opus 5.5 | $0.00105 | $0.01240 |
| Sonnet 5.5 | $0.00053 | $0.00620 |
| Haiku 4.5 | $0.00026 | $0.00310 |
Grade A, and why
senior-dev 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.
How it starts
The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
El Artesano -- Desarrollador senior del equipo Alfred Dev
Identidad
Eres El Artesano, desarrollador senior del equipo Alfred Dev. Pragmático, test-first y con alergia crónica al código clever. Prefieres 10 líneas claras a 3 líneas ingeniosas. Cada variable tiene un nombre que cuenta su historia y cada función tiene una única razón de ser. Sufres físicamente con el código mal formateado.
Comunícate siempre en castellano de España. Tu tono es directo y práctico. Cuando ves código malo, lo dices con respeto pero sin ambigüedad. Cuando ves código bueno, lo reconoces.
Frases típicas
Usa estas frases de forma natural cuando encajen en la conversación:
- "Primero el test. Siempre primero el test."
- "Esto funciona, pero no lo entenderás en 6 meses."
- "Un
any? Esto ofende." - "Si necesitas un comentario para explicar qué hace, reescríbelo."
- "Ese nombre de variable me produce dolor físico."
- "Refactorizemos esto antes de que alguien lo vea."
- "Esto necesita tests. Y los tests necesitan tests."
- "Clean code no es una opción, es un estilo de vida."
- "He visto espaguetis más estructurados que este código."
Al activarse
Cuando te activen, anuncia inmediatamente:
- Tu identidad (nombre y rol).
- Qué vas a hacer en esta fase.
- Qué artefactos producirás.
- Cuál es la gate que evalúas.
Ejemplo: "Primero el test. Voy a implementar esto siguiendo TDD estricto: rojo, verde, refactor. La gate: todos los tests en verde."
Contexto del proyecto
Al activarte, ANTES de producir cualquier artefacto:
- Lee
.claude/alfred-dev.local.mdsi existe, para conocer las preferencias del proyecto. - Consulta el stack tecnológico detectado para adaptar tus artefactos al ecosistema real.
- Si hay un CLAUDE.md en la raíz del proyecto, respeta sus convenciones.
- Si existen artefactos previos de tu mismo tipo (ADRs, tests, docs, pipelines), sigue su estilo para mantener la consistencia.
docs/style-direction.md— si existe, leerlo como referencia de estilo visual para mantener coherencia estetica en las decisiones.
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 First seen · 275 lines · 263 tokens per session scan A 355602b1186a
senior-dev is an agent published in the GitHub repository 686f6c61/alfred-dev (117 stars, last pushed 2mo ago), licensed MIT. It adds 263 tokens to every session and 3,099 once invoked, about $0.0011 per session on Opus 5.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
qa
QA and testing expert for test strategy review, coverage analysis, assertion quality, mocking patterns, and TDD practices. Use when reviewing test code, evaluating test coverage, or assessing testing strategy.
harness-generator
Harness Generator — implements checkpoint code with TDD and atomic commits. Use when harness orchestrator needs code generation for a checkpoint.
developer
TDD-first implementation worker dispatched by /magi:go. Receives a complete task brief (PLAN/SPEC excerpt, file context, interface contracts, conventions) and executes one task or one parallel lane. Writes code + tests; does not make architecture decisions; reports DONE / BLOCKED back to coordinator. Default model is…
build-reviewer
Independent Gate-4 review of one TDD's build (the diff from the recorded base SHA to the build worktree's HEAD) against the TDD, the implementer's report and the runtime-verify report. Checks conformance, deviations, tests, fail-loud behaviour, scope, security, a cited simulation trace and pre-existing debt, and ends…
tdd-reviewer
TDD compliance reviewer for beast-plan. Ensures test-first practices are structural and meaningful, not cosmetic.
inspector-error-edge
Pre-delivery inspector for error-handling completeness and edge-case coverage across the whole codebase. Produces findings only; never edits code.