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/generate-prpgit clone --depth 1 https://github.com/cveralyon/axel-setupWrote 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/cveralyon/axel-setup/generate-prp)<a href="https://agentmods.dev/commands/cveralyon/axel-setup/generate-prp"><img src="https://agentmods.dev/badge/commands/cveralyon/axel-setup/generate-prp.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.1 | $0.00000 | $0.00621 |
| Opus 5 | $0.00000 | $0.00311 |
| Sonnet 5 | $0.00000 | $0.00124 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
generate-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 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate PRP
Lee INITIAL.md en el directorio actual y genera un PRP (Product Requirements Prompt) completo
que sirva como blueprint de implementación autosuficiente.
Proceso obligatorio
1. Lee INITIAL.md
Entiende exactamente qué se quiere construir, el contexto de negocio y los criterios de aceptación.
2. Explora el codebase sin asumir nada
Antes de escribir una sola línea del PRP, ejecuta en paralelo:
- Lee
.claude/rules/completo para entender todas las restricciones activas - Busca con Grep/Glob archivos similares a lo que se va a construir (modelos, servicios, hooks, etc.)
- Lee los archivos más relevantes que el PRP referenciará como ejemplos
- Si hay
docs/con documentación técnica, léela en la sección relevante
3. Genera el PRP en PRPs/<feature-slug>.md
El slug del archivo debe ser kebab-case descriptivo (ej: PRPs/candidate-enrichment.md).
Estructura del PRP a generar
# PRP: [Nombre de la Feature]
## Goal
Qué construir y por qué — conectar con el impacto de negocio en tu proyecto.
## Context
### Archivos clave a leer antes de implementar
Lista de paths absolutos (relativos al repo) con descripción de por qué son relevantes.
### Patrones a seguir
Referencias concretas: "sigue el patrón de X para hacer Y" con paths exactos.
### Restricciones activas
Reglas de `.claude/rules/` que aplican directamente a esta feature (no las repitas, solo referencialas).
## Implementation Plan
Pasos ordenados. Cada paso debe tener:
- Acción concreta
- Path exacto del archivo
- Qué leer primero si aplica
### Paso 1: [Nombre]
...
### Paso N: Tests
Qué specs escribir, qué casos cubrir (happy path, edge cases, unauthorized, not found).
## API Contract (si aplica)
Endpoint, método HTTP, request body, response body, status codes.
## Validation Checklist
- [ ] Todos los tests pasan (`RAILS_ENV=test bundle exec rspec` o `pnpm check`)
- [ ] Sin N+1 queries
- [ ] Lint pasa
- [ ] Criterios de aceptación de INITIAL.md cumplidos
- [ ] Soft delete implementado si aplica (Paranoia)
- [ ] Pundit policy actualizada si aplica
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 · 76 lines · 0 tokens per session scan A c48eb53b866e
generate-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 621 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.