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-sprint-plangit 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-sprint-plan)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-sprint-plan"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-sprint-plan/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-sprint-plan"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-sprint-plan.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.00025 | $0.00916 |
| Opus 5.5 | $0.00010 | $0.00366 |
| Sonnet 5.5 | $0.00005 | $0.00183 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
quinotospec-sprint-plan 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 1mo 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Este workflow analiza el estado del proyecto y genera una propuesta de Sprint Plan para el equipo.
Parámetros Requeridos:
SPRINT_ID: Identificador del sprint (ej.1)
Paso 1 — Validar configuración
- Verifica que exista
.quinoto-spec/sprints/base-config.yml. Si no existe → ejecuta@quinotospec.sprints.init. - Verifica que exista
.quinoto-spec/sprints/sprint-{{SPRINT_ID}}/sprint-config.yml. Si no existe → ejecuta@quinotospec.sprint.create. - Lee ambos archivos de configuración.
Paso 2 — Cálculo de capacidad real
Con base en la unión de base-config.yml y sprint-config.yml:
- Calcula la capacidad total del sprint:
- Si
velocidad_promedio_puntostiene valor → usarlo directamente. - Si no → calcular:
sum(disponibilidad de cada miembro) × días hábiles del sprint × factor de carga(asumir ~5 puntos/día por desarrollador a tiempo completo).
- Si
- Reporta: "Capacidad calculada: [N] puntos para [N] semanas con [N] integrantes."
Paso 3 — Lectura del estado actual
- Lee
PROJECT_STATUS.mdsi existe. - Escanea
.quinoto-spec/proposals/para identificar todas las propuestas activas y su porcentaje de completitud. - Para cada propuesta activa, lista las user stories pendientes y sus tareas con prioridad y estimación.
Paso 4 — Selección de ítems para el sprint
- Prioriza en este orden:
- Tareas de propuestas listadas en
prioridad_propuestas(en el orden especificado). - Tareas P1 de propuestas en estado 🟢 (En Curso) no listadas arriba.
- Tareas P1 de propuestas en estado 🟡 (Propuesta) no listadas arriba.
- Tareas P2 si queda capacidad.
- Tareas de propuestas listadas en
- Respeta las Dependencias declaradas en los archivos de tareas.
- Al asignar tareas, considera el
rol,componentes_permitidosycomponente_ownerde cada integrante del equipo. - No exceder la capacidad total calculada en el Paso 2.
Paso 5 — Generación del Sprint Plan
Genera el archivo .quinoto-spec/sprints/sprint-{{SPRINT_ID}}/sprint-plan.md con el siguiente formato:
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.
- 1mo ago First seen · 87 lines · 25 tokens per session scan A e082da35a98a
quinotospec-sprint-plan is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (21 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 916 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.