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 commands/686f6c61/alfred-dev/uatgit 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/commands/686f6c61/alfred-dev/uat)<a href="https://agentmods.dev/commands/686f6c61/alfred-dev/uat"><img src="https://agentmods.dev/badge/commands/686f6c61/alfred-dev/uat.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.00019 | $0.00616 |
| Opus 5 | $0.00010 | $0.00308 |
| Sonnet 5 | $0.00004 | $0.00123 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
uat 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/alfred-dev:uat
Eres Alfred. Tu trabajo aquí es cerrar la validación humana del entregable, no reinterpretar los tests automáticos.
Argumento libre del usuario: $ARGUMENTS
Semántica del comando
- Sin argumento: prepara o refresca la UAT actual y deja el checklist listo.
aprobado ...: registra que la validación manual ha quedado aprobada.rechazado ...: registra que la validación manual ha fallado y guarda la nota.pendiente ...: reabre o reinicia la UAT para volver a pasarla.
Protocolo
- Como
.claude/*es sensible en Claude Code, NO usesWriteniEditpara los artefactos de UAT. Usa Bash y el helper del plugin inmediatamente:
python3 .claude/alfred-continuity.py verify "$PWD" --raw "$ARGUMENTS"
-
Ese helper debe crear o actualizar estos artefactos:
.claude/alfred-uat.jsondocs/project/uat.md
-
Si el helper devuelve una respuesta válida, úsala como respuesta final y termina. El helper ya deja visibles el estado, el objetivo, el checklist, las notas y el siguiente paso.
-
Solo si el helper falla, cae al modo manual y entonces lee este contexto en este orden:
.claude/alfred-dev-state.json.claude/alfred-handoff.json.claude/alfred-uat.jsonsi existedocs/project/current.mdsi existedocs/project/codebase-map.mdsi existedocs/project/uat.mdsi existe
-
Si existe una sesión activa y
fase_actualNO escompletado, NO inventes una aceptación manual prematura. Indica que primero hay que cerrar o retomar ese flujo con/alfred-dev:resumeo/alfred-dev:next.
Restricciones
- NO uses
AskUserQuestioncomo paso obligatorio dentro de/alfred-dev:verify. - NO marques una UAT como aprobada sin una indicación explícita del usuario.
- NO borres el estado del flujo completado que originó la validación.
- NO añadas una segunda capa de resumen si el helper ya dejó
Estado,Objetivo,Checklist,NotasySiguiente paso. - Si la UAT queda pendiente, termina indicando cómo registrar el resultado:
/alfred-dev:verify aprobadoo/alfred-dev:verify rechazado <nota>.
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 · 59 lines · 19 tokens per session scan A f29aa7031db0
uat is a command published in the GitHub repository 686f6c61/alfred-dev (119 stars, last pushed 19d ago), licensed MIT. It adds 19 tokens to every session and 616 once invoked, about $0.0001 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 commands, from other repositories
cdd-pre-pr
Run a pre-PR checklist for the current branch. Compare against the base branch to identify all changes. This is a verification session: it runs CI gates, code-reviews the diff, and reconciles documentation against the changes.
cdd-retrofit
Install CDD into an existing project, or upgrade a project already running CDD, at the path given as argument: /cdd-retrofit .
cdd-process-pr
Address the open PR's review feedback: read the review comments for the current branch, triage them, implement the change-requests (pushing back where warranted), then auto-post in-thread replies and auto-commit + push the result.
cdd-quick-create
Produce a small, self-contained deliverable — a script plus a README, not a full CDD project: /cdd-quick-create (takes an optional one-line description of what to build).
init-project
Initialize a new or upgrade existing project with Alpha AI's standard architecture. Supports Python/FastAPI, Node.js/NestJS, Java/Spring Boot. Usage: /init-project [--lang=python|nestjs|springboot] [--with-frontend] [--with-mobile] [--with-ai] [--existing].
accessibility
Audit frontend for WCAG 2.1 AA compliance: check semantic HTML, ARIA labels, color contrast, keyboard navigation, screen reader support. Usage: /accessibility [page-or-component] [--fix] [--level=AA|AAA].