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 skills add josemerca/mercadona-user-story-toolkit --skill gsd-to-prdgit 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/skills/josemerca/mercadona-user-story-toolkit/gsd-to-prd)<a href="https://agentmods.dev/skills/josemerca/mercadona-user-story-toolkit/gsd-to-prd"><img src="https://agentmods.dev/badge/skills/josemerca/mercadona-user-story-toolkit/gsd-to-prd/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/skills/josemerca/mercadona-user-story-toolkit/gsd-to-prd"><img src="https://agentmods.dev/badge/skills/josemerca/mercadona-user-story-toolkit/gsd-to-prd.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.00190 | $0.02442 |
| Opus 5 | $0.00095 | $0.01221 |
| Sonnet 5 | $0.00038 | $0.00488 |
| Haiku 4.5 | $0.00019 | $0.00244 |
Grade A, and why
gsd-to-prd 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 12d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GSD → PRD — Mapeo de artefactos
Asiste al usuario en transformar los artefactos generados por GSD en un PRD sintético, marcando explícitamente los gaps que GSD no cubre.
Filosofía: El PRD generado es fiel pero incompleto. GSD captura contexto, scope y fases con criterios de aceptación, pero NO captura métricas con baseline, citas cualitativas, o ROI. Esos gaps se marcan para que el PM los complete tras
/research.
Principio Fundamental
┌─────────────────────────────────────────────────────────────────┐
│ │
│ GSD captura GSD NO captura │
│ ──────────── ───────────── │
│ │
│ ✅ Contexto del producto ❌ Métricas con baseline │
│ ✅ Requirements v1/v2 ❌ Citas de usuarios │
│ ✅ Out of scope ❌ ROI / aspectos financ. │
│ ✅ Fases con success criteria ❌ FAQs anticipadas │
│ ✅ Specs por fase ❌ Penumbras (cualitativo) │
│ ✅ Research previo (si lo hay) ❌ Farolas (cuantitativo) │
│ │
└─────────────────────────────────────────────────────────────────┘
GSD opera con principios falsables y testeables. el PRD opera con evidencia cualitativa y cuantitativa. El bridge respeta ambos: rellena lo que se puede mapear, marca lo que falta.
Flujo de Generación
.planning/ (GSD)
│
▼
┌──────────────────────────────────────┐
│ 1. VALIDAR ARTEFACTOS │
│ - PROJECT.md (REQ) │
│ - REQUIREMENTS.md (REQ) │
│ - ROADMAP.md (REQ) │
│ - phases/N/SPEC.md (OPT) │
│ - phases/N/RESEARCH.md (OPT) │
└──────────────────────────────────────┘
│
▼
┌──────────────────────────────────────┐
│ 2. APLICAR MATRIZ DE MAPEO │
│ Ver references/mapping-table.md │
└──────────────────────────────────────┘
│
▼
┌──────────────────────────────────────┐
│ 3. RELLENAR SECCIONES MAPEABLES │
│ - 1.1 Problema (de PROJECT) │
│ - 1.4 Próximos pasos (de ROADMAP) │
│ - 2.1 Hipótesis (de SPEC.Goal) │
│ - 2.4 Dimensionamiento (ROADMAP) │
│ - 3.1 Discovery (RESEARCH si hay) │
│ - 3.2 Explore (Key Decisions) │
│ - 3.3 Funcionalidades (REQ + SPEC)│
│ - 3.4 Flujos (de SPEC si los hay) │
│ - 3.6 Exclusiones (REQ Out-Scope) │
└──────────────────────────────────────┘
│
▼
┌──────────────────────────────────────┐
│ 4. MARCAR GAPS EXPLÍCITOS │
│ - 1.2 Farolas → ⚠️ GAP │
│ - 1.3 Penumbras → ⚠️ GAP │
│ - 2.2 Aspectos financieros → ⚠️ │
│ - 2.3 Métricas baseline→target ⚠️│
│ - 3.5 FAQs → ⚠️ GAP │
└──────────────────────────────────────┘
│
▼
┌──────────────────────────────────────┐
│ 5. GENERAR prd-from-gsd.md │
│ - Header con metadata origen │
│ - 14 secciones (rellenas+gaps) │
│ - Footer con resumen+next steps │
└──────────────────────────────────────┘
│
▼
PRD sintético listo para /prd-quality-guard
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 208 lines · 190 tokens per session scan A 7d9edd175cdb
gsd-to-prd is a skill published in the GitHub repository josemerca/mercadona-user-story-toolkit (25 stars, last pushed 4mo ago), licensed MIT. It adds 190 tokens to every session and 2,442 once invoked, about $0.0010 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…