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-debuggit 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-debug)<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-debug"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-debug/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-debug"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-debug.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.00030 | $0.01070 |
| Opus 5.5 | $0.00012 | $0.00428 |
| Sonnet 5.5 | $0.00006 | $0.00214 |
| Haiku 4.5 | $0.00003 | $0.00107 |
Grade A, and why
quinotospec-debug 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: QuinotoSpec Debug
Iron Law
No apliques un parche hasta tener una hipótesis reproducible y evidencia que identifique la causa raíz.
Un hotfix sin causa raíz puede ocultar el defecto, mover el fallo o crear una segunda regresión.
Método de cuatro fases
1. Reproducir
- Captura el comando exacto, entrada, entorno y salida.
- Reduce el caso a un test o fixture mínimo.
- Confirma la línea base y la frecuencia del fallo.
- Si no puedes reproducirlo, no cambies producción todavía.
2. Localizar
- Traza la entrada desde el límite público hasta el primer valor incorrecto.
- Revisa logs, trazas de pila, límites, estado compartido y llamadas externas.
- Separa el síntoma del punto donde se origina.
- Usa
root-cause-tracing.mdcuando el flujo cruce varios módulos.
3. Formular y probar hipótesis
Escribe una hipótesis falsable:
Si <condición> es la causa, entonces <observación> cambiará al <experimento>.
- Cambia una variable por experimento.
- Registra resultado, expectativa y conclusión.
- No mezcles varios cambios en un experimento.
- Tras tres hipótesis fallidas, detén los parches locales y pregunta si la arquitectura o el contrato es incorrecto.
4. Corregir y verificar
- Escribe o ajusta un test que falle por la causa raíz.
- Implementa la corrección mínima en la capa responsable.
- Ejecuta el test focalizado, la suite afectada y los comandos de calidad.
- Añade defensa en profundidad solo si el límite necesita protección.
- Registra causa raíz, corrección y evidencia.
Registro verificable
Guarda un registro JSON en .quinoto-spec/evidence/{{TASK_ID}}/debug.json con schema_version, task_id, recorded_at, reproduction, hypothesis, experiment, root_cause y regression. Los bloques de ejecución incluyen command, status, exit_code y output; la regresión debe terminar en passed.
python3 -B agent-dist/skills/quinotospec-rules-enforce/evidence_validate.py validate \
--root . --kind debug --task-id {{TASK_ID}} --require --json
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 106 lines · 30 tokens per session scan A d78a7af13186
quinotospec-debug is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (21 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 1,070 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-26.
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.
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…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.