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-fixgit 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-fix)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-fix"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-fix/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-fix"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 17 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 25 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 71 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 123 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.01203 |
| Opus 5 | $0.00013 | $0.00602 |
| Sonnet 5 | $0.00005 | $0.00241 |
| Haiku 4.5 | $0.00003 | $0.00120 |
Grade A, and why
quinotospec-fix 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow: Fix
[INSTRUCCIÓN MAESTRA] Debes corregir el bug o implementar el fix menor descrito por el usuario, documentar los cambios y ejecutar los tests correspondientes. Este workflow está pensado para bugs y fixes que no requieren una propuesta técnica formal.
Parámetros:
| Parámetro | Requerido | Descripción |
|---|---|---|
| Descripción del bug/fix | Sí | Qué problema hay y qué comportamiento se espera |
--task TASK_ID |
No | Si el fix pertenece a una tarea existente en una propuesta |
--skip-tests |
No | Omitir ejecución de tests (solo para cambios triviales) |
Invocación:
@quinotospec.fix "El botón de logout no cierra la sesión correctamente"
@quinotospec.fix "Corregir validación de email en el formulario de registro"
@quinotospec.fix --task TSK-AUTH-003 "Agregar manejo de error en el catch block"
@quinotospec.fix --skip-tests "Corregir typo en mensaje de bienvenida"
Paso 0 — Análisis del Bug
-
Leer la descripción del bug/fix proporcionada por el usuario.
-
Si se pasó
--task TASK_ID:- Buscar la tarea en
.quinoto-spec/proposals/{PROPOSAL_SLUG}/{US_ID}_tasks.md - Leer el contexto técnico, criterios de aceptación y detalles de implementación
- El fix debe alinearse con lo definido en la tarea
- Buscar la tarea en
-
Si NO se pasó
--task:- Es un fix independiente. Crear contexto en
.quinoto-spec/fixes/YYYYMMDD-hhmm-{slug}.md - El archivo de contexto debe contener:
# Fix: {slug} - **Fecha**: YYYY-MM-DD HH:MM - **Descripción**: {descripción del bug} - **Comportamiento esperado**: {qué debería pasar} - **Comportamiento actual**: {qué pasa ahora} - **Stack detectado**: {lenguaje, framework, test runner}
- Es un fix independiente. Crear contexto en
-
Leer
.quinoto-spec/discovery/01-stack-profile.md(si existe) para conocer el stack, comandos de test y convenciones. -
Identificar los archivos involucrados en el bug.
-
Presentar análisis al usuario antes de tocar código (BLOQUEANTE):
- Archivos que se modificarán
- Causa raíz identificada
- Solución propuesta (1-2 líneas)
- Riesgo del cambio (BAJO / MEDIO / ALTO)
- Preguntar: "¿Procedo con el fix?"
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 · 126 lines · 25 tokens per session scan A 2623425a1607
quinotospec-fix 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,203 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.