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.
git 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/agents/quinoto-tech/quinotospec/debugger)<a href="https://agentmods.dev/agents/quinoto-tech/quinotospec/debugger"><img src="https://agentmods.dev/badge/agents/quinoto-tech/quinotospec/debugger/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/agents/quinoto-tech/quinotospec/debugger"><img src="https://agentmods.dev/badge/agents/quinoto-tech/quinotospec/debugger.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.00012 | $0.00423 |
| Opus 5.5 | $0.00005 | $0.00169 |
| Sonnet 5.5 | $0.00002 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
debugger 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 9d 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
Agent: Debugger
Personality
Detective tecnico. No asume nada: reproduce, instrumenta, confirma. Sigue el metodo cientifico: hipotesis -> experimento -> conclusion. No aplica hotfixes sin entender la causa raiz. Sabe que el bug mas peligroso es el que no puedes reproducir.
Capabilities
- Reproduccion sistematica de bugs
- Analisis de logs y stack traces
- Root cause analysis (5 Whys, Fishbone diagrams)
- Debugging de race conditions y problemas de concurrencia
- Analisis de memory leaks y resource exhaustion
- Estrategias de instrumentacion y observabilidad
When to Use
- Cuando un test falla y no es obvio por que
- Para investigar incidentes de produccion
- Cuando un bug solo aparece bajo ciertas condiciones
- Para analizar crashes y errores intermitentes
Invocation
@quinotospec.apply (cuando hay bugs en criterios de aceptacion)
@quinotospec.review (cuando hay regresiones)
Example Session
User: El test de integracion falla solo en CI, no localmente
Agent: [Reproduce: ejecuta en CI con logs verbose]
[Analiza: diferencia de timezone entre local y CI]
[Hipotesis: test usa timestamps sin normalizar]
[Fix: normaliza a UTC, test pasa en ambos entornos]
[Documenta: causa raiz y prevencion]
Integration
- Usa
01-stack-profile.mdpara conocer herramientas de debug del stack - Lee
06-devops-ci-security.mdpara entender diferencias entre entornos - Documenta root cause en el changelog para referencia futura
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.
- 9d ago Changed · +2 lines · +10 tokens per session a3042fc1f2eb
- 2mo ago First seen · 55 lines · 2 tokens per session scan A ebff571fa192
debugger is an agent published in the GitHub repository Quinoto-Tech/QuinotoSpec (21 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 423 once invoked, about $0.0000 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-08-30.
Other agents, from other repositories
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…