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-review-handoffgit 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-review-handoff)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-review-handoff"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-review-handoff/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-review-handoff"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-review-handoff.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.00046 | $0.01797 |
| Opus 5.5 | $0.00018 | $0.00719 |
| Sonnet 5.5 | $0.00009 | $0.00359 |
| Haiku 4.5 | $0.00005 | $0.00180 |
Grade A, and why
quinotospec-review-handoff 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 today.
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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow: Review Handoff
Este workflow se ejecuta cuando una propuesta esta completada (todas sus tareas corrieron) y antes de /quinotospec.archive. Genera un archivo autonomo — CODE_REVIEW_GUIDE.md — que sirve de guia a la persona que hara el code review, consolidando en un solo documento todo el contexto disperso de .quinoto-spec/ y del historial git.
⚠️ Orden del ciclo:
apply→mark-done→review-handoff(esta skill) → code review humano (feedback viaquinotospec-receive-review) →archive.
Diferencia con /quinotospec.review: ese workflow hace que el agente revise una tarea/branch contra sus criterios. Esta skill no revisa codigo: prepara el terreno para que un humano revise la propuesta completa con todo el contexto necesario.
Parametros Requeridos:
PROPOSAL_SLUG: El slug de la propuesta completada (ej.2026-09-24-add-login).
Flags:
| Flag | Descripcion |
|---|---|
--force |
Genera la guia aunque queden tareas pendientes; el gap queda documentado en la seccion de completitud |
--full-diff |
Incluye el diff completo inline en la seccion de git (por defecto solo --stat y --name-status) |
--output PATH |
Escribe una copia adicional de la guia en PATH (ej. raiz del repo para entregarsela al reviewer) |
--archived |
Busca la propuesta en .quinoto-spec/proposals/_archived/{{PROPOSAL_SLUG}}/ |
Instrucciones:
-
Localizar la propuesta y validar completitud (OBLIGATORIO):
- Localiza la propuesta en
.quinoto-spec/proposals/{{PROPOSAL_SLUG}}/; si no existe y se paso--archived, busca en.quinoto-spec/proposals/_archived/{{PROPOSAL_SLUG}}/. Si no existe, notifica al usuario y detente. - Recupera el Prefijo y la Fecha de Creacion desde
proposal.md. - Ejecuta
python3 -B agent-dist/skills/quinotospec-contract/contract.py inspect --root . --jsony filtra las tareas de la propuesta por prefijo. - Gate de completitud: si hay tareas
pending,blockedoin_progress→ muestra el conteo y la lista; genera la guia solo con--force(documentando el gap); sin--force, detente y sugiere/quinotospec.apply {{NEXT_TASK_ID}}. - Evidencia por tarea: verifica
.quinoto-spec/evidence/{{TASK_ID}}/; una tarea sin evidencia genera⚠️en la guia (advertencia, no bloqueo). - Advertencias de contexto (se registran en la guia, no bloquean): discovery obsoleto (>30 dias), constitucion ausente (si esta
active, lee sus principios para el checklist).
- Localiza la propuesta en
-
Recolectar contexto (en la carpeta de la propuesta y en su
_archived/—mark-donemueve alli los completados):proposal.md→ titulo, estado, prioridad, complejidad, servicios afectados, resumen, alcance, riesgos, criterios de exito.user-stories.md→ stories con sus criterios de aceptacion.*_tasks.md→ tabla de tareas: ID, titulo, Archivos a Modificar, dependencias, estado..quinoto-spec/evidence/{{TASK_ID}}/→ que se verifico por tarea.delta-specs/*/spec.md(si existe) → requerimientos ADDED / MODIFIED / REMOVED / RENAMED..quinoto-spec/discovery/01-stack-profile.md→ comandos de tests / lint / typecheck.- Changelog de la propuesta:
python3 -B agent-dist/skills/quinotospec-contract/contract.py changelog --root . --jsonfiltrado por el prefijo.
-
Analizar cambios en git:
- Identifica branches por convencion (
git branch --list '*{{PREFIX}}*'; patronesfeature/TSK-{{PREFIX}}-*/bugfix/TSK-{{PREFIX}}-*). - Determina la rama base (
maino la rama por defecto). - Por branch:
git log --oneline,git diff --name-status,git diff --stat(rango{{BASE}}..{{HEAD}}). - Mapea tarea → commits por nombre de branch o mencion del ID en el mensaje; sin mapeo →
⚠️. - Compara archivos declarados vs reales; marca
⚠️cualquier archivo real no declarado. - Fallback sin branches del prefijo:
git log --since="{{FECHA_DE_CREACION}}" --oneline --name-onlyfiltrando por archivos declarados.
- Identifica branches por convencion (
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.
- today First seen · 84 lines · 46 tokens per session scan A 79ebe8d67502
quinotospec-review-handoff is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (21 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 1,797 once invoked, about $0.0002 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-10-29.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
hero-diff-highlight
A dark code editor reveals a red deletion then a green addition with a soft pulse. Function: PR / code-change explainer.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.