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/split-stories)<a href="https://agentmods.dev/commands/josemerca/mercadona-user-story-toolkit/split-stories"><img src="https://agentmods.dev/badge/commands/josemerca/mercadona-user-story-toolkit/split-stories/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/split-stories"><img src="https://agentmods.dev/badge/commands/josemerca/mercadona-user-story-toolkit/split-stories.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.00015 | $0.00468 |
| Opus 5 | $0.00008 | $0.00234 |
| Sonnet 5 | $0.00003 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
split-stories 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.
Analiza stories para detectar red flags lingüísticos y propone splits incrementales.
Input necesario: User stories a analizar (de /stories, /validate-stories o de tu issue tracker).
Proceso:
- Leer el SKILL.md de
skills/story-splitting/ - Para cada story:
- Escanear las 6 categorías de red flags lingüísticos (
scripts/redflags.py) - Generar 2-3 propuestas alternativas con técnicas distintas (cast-wide). Ej: una vertical por flujo de usuario, una por capacidad, una por valor mínimo viable.
- Para cada alternativa, presentar: técnica aplicada, splits resultantes, trade-offs (qué se entrega antes / qué se aprende / qué riesgo cubre)
- CHECKPOINT: preguntar al usuario cuál prefiere antes de detallar splits
- Detallar los 3-5 splits de la opción elegida
- Escanear las 6 categorías de red flags lingüísticos (
- Generar reporte con:
- Diagnóstico de red flags
- Las alternativas exploradas (con la elegida marcada)
- Splits propuestos (en formato User Story)
- Orden de entrega recomendado
- Impacto esperado en Dim 6 (Survivable Experiment)
Output: Stories divididas en incrementos pequeños, seguros y valiosos, listas para tu issue tracker.
Nota: Si las stories ya tienen Score Dim 6 ≥8, el splitting es opcional. Se recomienda ejecutar siempre después de /validate-stories para asegurar granularidad óptima.
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 · 15 tokens per session scan A e8a65a09a134
split-stories is a command published in the GitHub repository josemerca/mercadona-user-story-toolkit (25 stars, last pushed 4mo ago), licensed MIT. It adds 15 tokens to every session and 468 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.