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/josemerca/mercadona-user-story-toolkitWrote 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/josemerca/mercadona-user-story-toolkit/from-gsd)<a href="https://agentmods.dev/commands/josemerca/mercadona-user-story-toolkit/from-gsd"><img src="https://agentmods.dev/badge/commands/josemerca/mercadona-user-story-toolkit/from-gsd/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/commands/josemerca/mercadona-user-story-toolkit/from-gsd"><img src="https://agentmods.dev/badge/commands/josemerca/mercadona-user-story-toolkit/from-gsd.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.00030 | $0.00565 |
| Opus 5 | $0.00015 | $0.00282 |
| Sonnet 5 | $0.00006 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
from-gsd 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 11d 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
Paso 0 (obligatorio): Cargar ground-rules. Antes de proceder, lee
shared-config.mdy aplica:
- §Filosofía del Plugin — modo copiloto, NO inventar, preguntar antes de generar
- §Estilo de Escritura — frases ≤30 palabras, sin adjetivos sin datos, NUNCA inventar métricas
- §Antipatrones Compartidos — los 7 antipatrones a detectar
Si no puedes leer el fichero, detén la ejecución y reporta el problema.
Ejecuta /from-gsd para transformar los artefactos de un proyecto GSD (Get Shit Done) en un PRD sintético compatible con /prd-quality-guard. El PRD resultante puede entrar al pipeline en la fase de research → stories.
Input necesario: Ruta al directorio .planning/ de un proyecto GSD. Default: ./.planning/ (directorio actual).
Proceso:
- Validar que existen los artefactos requeridos:
PROJECT.md,REQUIREMENTS.md,ROADMAP.md - Leer también (si existen):
phases/*/SPEC.md,phases/*/RESEARCH.md,STATE.md - Cargar el SKILL.md de
skills/gsd-to-prd/ - Aplicar la matriz de mapeo GSD → PRD (referencia:
mapping-table.md) - Generar fichero
prd-from-gsd.mden la raíz del proyecto - Marcar explícitamente las secciones que GSD no cubre (gaps)
- Reportar resumen: secciones rellenas + gaps a completar
Output: Fichero prd-from-gsd.md listo para /prd-quality-guard.
Importante:
- El PRD generado es sintético: refleja lo que GSD captura, NO sustituye discovery
- Si GSD ya tiene
RESEARCH.mdpor fase, se referencia como evidencia previa para/research - El comando NO modifica los ficheros GSD — solo lee
- El comando NO inventa datos: secciones sin equivalente en GSD se marcan como
⚠️ GAP
Siguiente paso: /prd-quality-guard prd-from-gsd.md → si PASS → /research source_type=PRD
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.
- 11d ago First seen · 36 lines · 30 tokens per session scan A a8d9736862dd
from-gsd is a command published in the GitHub repository josemerca/mercadona-user-story-toolkit (25 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 565 once invoked, about $0.0002 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
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.