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-creategit 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-create)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-sprint-create"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-sprint-create/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-create"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-sprint-create.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.00019 | $0.00551 |
| Opus 5 | $0.00010 | $0.00275 |
| Sonnet 5 | $0.00004 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
quinotospec-sprint-create 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 3d 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
Este workflow crea un nuevo sprint con su configuración inicial.
Parámetros Requeridos:
SPRINT_ID: Identificador del sprint (ej.1)NOMBRE_SPRINT: Nombre del sprint (ej.Integración Rapiboy)
Paso 1 — Crear estructura de carpetas
- Verifica si existe
.quinoto-spec/sprints/. Si no existe, ejecuta@quinotospec.sprints.initprimero. - Crea la carpeta
.quinoto-spec/sprints/sprint-{{SPRINT_ID}}/. - Crea la subcarpeta
.quinoto-spec/sprints/sprint-{{SPRINT_ID}}/proposals/.
Paso 2 — Crear configuración del sprint
Verifica si existe .quinoto-spec/sprints/sprint-{{SPRINT_ID}}/sprint-config.yml:
A. Si el archivo NO existe:
- Créalo con el esquema de referencia.
# Detalles del Sprint específico
id_sprint: {{SPRINT_ID}}
nombre_sprint: "{{NOMBRE_SPRINT}}"
duracion_semanas: 2
fecha_inicio: YYYY-MM-DD
# Prioridad de propuestas (slugs en orden de importancia)
prioridad_propuestas:
- ""
- Notifica al usuario: "Se ha creado la estructura del Sprint {{SPRINT_ID}}: '{{NOMBRE_SPRINT}}'. Archivo de configuración:
.quinoto-spec/sprints/sprint-{{SPRINT_ID}}/sprint-config.yml. Por favor, completa la información de fechas y prioridad de propuestas." - Instrucción Final OBLIGATORIA (Changelog): DEBES ejecutar la skill
quinotospec-update-changelog.- Título de la Acción: Sprint Creado: Sprint {{SPRINT_ID}} — {{NOMBRE_SPRINT}}
- Resumen: Se creó la estructura del Sprint {{SPRINT_ID}} ('{{NOMBRE_SPRINT}}') en
.quinoto-spec/sprints/sprint-{{SPRINT_ID}}/.
B. Si el archivo ya existe:
- Notifica al usuario: "El Sprint {{SPRINT_ID}} ya existe. Archivo:
.quinoto-spec/sprints/sprint-{{SPRINT_ID}}/sprint-config.yml" - No hubo cambios de estado — omite el registro en changelog.
Próximo paso: Usar @quinotospec.sprint.plan para planificar las tareas del sprint.
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.
- 3d ago Changed · +4 lines 62f51da62837
- 9d ago First seen · 49 lines · 19 tokens per session scan A 9452cc0974fe
quinotospec-sprint-create is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (20 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 551 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-09-03.
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.