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 cruzs85/opencode-multiagente-local-37-iterations --skill bug-investigationgit clone --depth 1 https://github.com/cruzs85/opencode-multiagente-local-37-iterationsWrote 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/cruzs85/opencode-multiagente-local-37-iterations/bug-investigation)<a href="https://agentmods.dev/skills/cruzs85/opencode-multiagente-local-37-iterations/bug-investigation"><img src="https://agentmods.dev/badge/skills/cruzs85/opencode-multiagente-local-37-iterations/bug-investigation/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/cruzs85/opencode-multiagente-local-37-iterations/bug-investigation"><img src="https://agentmods.dev/badge/skills/cruzs85/opencode-multiagente-local-37-iterations/bug-investigation.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.00000 | $0.00635 |
| Opus 5 | $0.00000 | $0.00318 |
| Sonnet 5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
bug-investigation 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.
What it actually says
Skill: bug-investigation
Objetivo
Protocolo de investigación de bugs para ahorrar tokens. Define cuándo el orquestador investiga directamente y cuándo delega a @explorer, junto con el formato de reporte que explorer debe devolver.
Para el ORQUESTADOR — Árbol de decisión
Cuando el usuario reporte un comportamiento incorrecto en la app, clasifica el bug:
Bug ACOTADO
Características:
- Sospecha clara de 1 solo archivo
- Síntoma específico y localizado
- Ej: "el botón no se ve", "el texto está mal alineado"
Acción: Lee el archivo sospechoso DIRECTAMENTE y resuelve. No delegues a explorer.
Bug DIFUSO
Características (cualquiera de estas):
- Involucra 2+ archivos (ej: servicio + componente)
- El flujo de datos cruza servicio y componente
- Es un error de integración o lógica distribuida
- No está claro dónde está la causa raíz
- Ej: "los obstáculos no aparecen", "la puntuación no coincide", "el movimiento se siente incorrecto"
Acción:
- DELEGA a @explorer la investigación
- Proporciónale: síntoma observable, archivos que creas relevantes (rutas completas), hipótesis inicial
- Pídele que cargue esta skill ('bug-investigation') para saber el formato de reporte
- Cuando recibas su reporte, diseña la solución y delega la corrección a @code-writer
Para @explorer — Formato de reporte obligatorio
Cuando el orquestador te delegue una investigación de bug, DEBES cargar esta skill y devolver el reporte en EXACTAMENTE este formato:
📋 REPORTE DE INVESTIGACIÓN DE BUG
🔍 Hipótesis investigada: [hipótesis que recibiste]
📁 Archivos revisados:
1. [ruta/archivo.ts] — [qué hace, líneas relevantes]
2. ...
🔬 Hallazgos:
| Archivo | Línea | Valor actual | Valor esperado | Tipo |
|---|---|---|---|---|
| ruta.ts | 42 | `código actual` | `código esperado` | lógica/sintaxis/integración |
🎯 Causa raíz:
[explicación de 1-3 líneas de por qué ocurre el bug]
💡 Solución propuesta:
[qué cambiar, en qué archivo, en qué línea]
Reglas de investigación:
- Lee los archivos que el orquestador te indique
- Si encuentras el bug, detén la búsqueda (no sigas revisando archivos adicionales sin necesidad)
- Si después de revisar los archivos sugeridos no encuentras el bug, revisa archivos relacionados (imports, dependencias)
- Máximo 3 intentos de búsqueda. Si no encuentras nada, reporta "No se encontró la causa raíz en los archivos investigados"
- No modifiques ningún archivo — solo reportas
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 · 66 lines · 0 tokens per session scan A 288a4c863d88
bug-investigation is a skill published in the GitHub repository cruzs85/opencode-multiagente-local-37-iterations (5 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 635 tokens. 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-31.
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.