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-distributegit 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-distribute)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-distribute"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-distribute/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-distribute"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-distribute.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.01073 |
| Opus 5 | $0.00013 | $0.00536 |
| Sonnet 5 | $0.00005 | $0.00215 |
| Haiku 4.5 | $0.00003 | $0.00107 |
Grade A, and why
quinotospec-distribute 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow: Distribute
Este workflow toma una propuesta centralizada (normalmente generada desde un stack-discovery o create-proposal) y distribuye sus artefactos hacia los .quinoto-spec/ de cada sub-proyecto afectado.
Parámetros Requeridos:
PROPOSAL_SLUG: El slug de la propuesta centralizada a distribuir (ej.stack-standardization).SPRINT_ID: El ID del sprint al que pertenecen las tareas (ej.1).
Paso 1 — Leer el plan de sprint y la propuesta
- Lee
.quinoto-spec/sprints/sprint-{{SPRINT_ID}}/sprint-plan.mdpara identificar qué tareas de la propuesta{{PROPOSAL_SLUG}}han sido asignadas a este sprint y a qué Componente (sub-proyecto) pertenecen. - Lee
.quinoto-spec/proposals/{{PROPOSAL_SLUG}}/proposal.mdy extrae:**Servicios Afectados:**→ lista de sub-proyectos destino.
- Lee
.quinoto-spec/proposals/{{PROPOSAL_SLUG}}/user-stories.mdy agrupa las user stories por la columna que coincida con el Componente (oServicio). - Lee todos los archivos
*_tasks.mdde la propuesta y agrupa las tareas por su columna Componente (oServicio), filtrando solo aquellas que están presentes en elsprint-plan.md.
Paso 2 — Validar sub-proyectos destino
Para cada servicio en Servicios Afectados:
- Verifica que la carpeta del sub-proyecto exista en el root.
- Verifica que tenga
.quinoto-spec/(si no existe, créala). - Si un servicio listado no existe como carpeta → notificar al usuario y saltar ese servicio.
Paso 3 — Distribuir artefactos por servicio
Para cada sub-proyecto destino, crear la siguiente estructura dentro de <servicio>/.quinoto-spec/sprints/sprint-{{SPRINT_ID}}/proposals/{{PROPOSAL_SLUG}}/:
Archivos a distribuir (copia literal)
Estos archivos se distribuyen sin modificación, haciendo copy-paste directo del original:
proposal.md→ copia literal de.quinoto-spec/proposals/{{PROPOSAL_SLUG}}/proposal.mduser-stories.md→ copia literal de.quinoto-spec/proposals/{{PROPOSAL_SLUG}}/user-stories.mdall_tasks.md→ copia literal de.quinoto-spec/proposals/{{PROPOSAL_SLUG}}/all_tasks.md(si existe)- Cada archivo
*_tasks.md→ copia literal de.quinoto-spec/proposals/{{PROPOSAL_SLUG}}/{{US_ID}}_tasks.md
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 · 89 lines · 25 tokens per session scan A cad129bcf1cd
quinotospec-distribute is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (20 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 1,073 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.