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/cveralyon/axel-setup/execute-prpgit clone --depth 1 https://github.com/cveralyon/axel-setupWhat 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.00000 | $0.00387 |
| Opus 5 | $0.00000 | $0.00193 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
execute-prp 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.
What it actually says
Execute PRP
Ejecuta el PRP especificado: $ARGUMENTS
Si no se pasa argumento, busca el PRP más reciente en PRPs/ o pregunta cuál ejecutar.
Proceso obligatorio
1. Lee el PRP completo
Antes de tocar un solo archivo, lee el PRP entero. Entiende el scope total.
2. Lee todos los archivos referenciados en "Context"
No asumas nada del código existente — lee los archivos mencionados en el PRP. Si el PRP dice "sigue el patrón de X", lee X antes de empezar.
3. Implementa paso a paso
Sigue el Implementation Plan en orden. Por cada paso:
- Implementa
- Si es un bloque lógico completo (modelo, servicio, controller, etc.), haz commit inmediato
- Commit format:
feat (Modelo/Archivo): Descripción— max 6 archivos por commit
4. Valida al finalizar
Corre el Validation Checklist del PRP ítem por ítem.
Reporta resultados antes de declarar la feature terminada.
5. Marca pasos completados en el PRP
Actualiza el PRP con ✅ en cada paso del Implementation Plan al completarlo.
Reglas de ejecución
- No saltes pasos — si un paso requiere leer algo primero, léelo
- No asumas que el PRP está actualizado — si encuentras discrepancias con el código real, actualiza el PRP y reporta
- Bloqueantes primero — si algo bloquea la implementación, repórtalo inmediatamente antes de continuar con pasos posteriores
- Tests no son opcionales — el paso de tests es parte de la implementación, no un extra
- Nunca
--no-verifyen ningún commit
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 · 38 lines · 0 tokens per session scan A c67e94f4cb3f
execute-prp is a command published in the GitHub repository cveralyon/axel-setup (4 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 387 tokens. 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.