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 Quinoto-Tech/QuinotoSpec --skill quinotospec-create-user-storiesgit clone --depth 1 https://github.com/Quinoto-Tech/QuinotoSpecWrote 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/quinoto-tech/quinotospec/quinotospec-create-user-stories)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-create-user-stories"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-create-user-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/skills/quinoto-tech/quinotospec/quinotospec-create-user-stories"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-create-user-stories.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00018 | $0.00842 |
| Opus 5 | $0.00009 | $0.00421 |
| Sonnet 5 | $0.00004 | $0.00168 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
quinotospec-create-user-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 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.
What it actually says
Workflow: Create User Stories
Este workflow genera user stories derivadas de una propuesta técnica existente.
Requiere que la propuesta (proposal.md) ya haya sido creada.
Parámetro Requerido:
PROPOSAL_SLUG: El nombre de la carpeta de la propuesta (ej.refactor-proposal-workflows).
Instrucciones:
- Lee el archivo
.quinoto-spec/proposals/{{PROPOSAL_SLUG}}/proposal.md. - Validación previa: Verifica que el
**Estado:**de la propuesta NO seaArchivada. Si lo es, notifica al usuario y detén el proceso. - Inferencia de roles: Identifica los roles involucrados a partir del contenido de la propuesta y de
01-stack-profile.mden el discovery (ej. usuario, admin, sistema, operador). Úsalos en las stories en lugar de[rol]genérico. - Cantidad de stories: Genera una story por cada funcionalidad o cambio sustancial de la propuesta. Ordénalas según las fases del Plan de Implementación definido en la propuesta.
- Merge inteligente: Si
.quinoto-spec/proposals/{{PROPOSAL_SLUG}}/user-stories.mdya existe, no sobreescribas. Revisa las stories existentes y realiza un merge: agrega solo las stories nuevas y actualiza las que hayan cambiado. - Genera el archivo en
.quinoto-spec/proposals/{{PROPOSAL_SLUG}}/user-stories.mdcon el siguiente formato:- Título: User Stories ({{PROPOSAL_NAME}}).
- Tabla con columnas: ID, User Story, Criterios de Aceptación, Prioridad, Estimación, Servicio.
- IDs: Busca el
**Prefijo:** {{PREFIX}}en el archivoproposal.md. Usa ese prefijo para los IDs:US-{{PREFIX}}-001. - Prioridad:
P1(alta) /P2(media) /P3(baja), según la fase y relevancia en la propuesta. - Estimación: Talla de camiseta (
XS/S/M/L/XL) según la complejidad estimada de la historia. - Servicio: El sub-proyecto o servicio donde se implementa esta historia, inferido de
**Servicios Afectados:**enproposal.md. Si la historia aplica a todos los servicios, usartodos. - Template:
# User Stories ({{PROPOSAL_NAME}}) | ID | User Story | Criterios de Aceptación | Prioridad | Estimación | Servicio | | --- | --- | --- | --- | --- | --- | | US-{{PREFIX}}-001 | Como **[rol]**, quiero **[acción]**, para **[beneficio/valor]**. | - [Criterio 1]<br>- [Criterio 2] | P1 | M | auth-service | | US-{{PREFIX}}-002 | Como **[rol]**, quiero **[acción]**, para **[beneficio/valor]**. | - [Criterio 1]<br>- [Criterio 2] | P2 | S | user-service |
Instrucción Final OBLIGATORIA (Changelog):
Una vez completada, DEBES ejecutar la skill quinotospec-update-changelog.
- Título de la Acción: User Stories Generated: {{PROPOSAL_NAME}}
- Resumen: Se generaron user stories para la propuesta '{{PROPOSAL_NAME}}' en .quinoto-spec/proposals/{{PROPOSAL_SLUG}}/
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 · 41 lines · 18 tokens per session scan A 6344ab6d0cab
quinotospec-create-user-stories is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (20 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 842 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.