What is bug-investigation?

A bug-investigation process that decides whether the problem can be traced to one file or requires examining several files. A diffuse bug may involve data moving through services, components, or other parts of the application.

Use it when the application behaves incorrectly to inspect a likely file directly, or to investigate multi-file integration and logic problems with a structured report.

It helps choose an efficient investigation path and prevents unnecessary delegation for simple, localized problems. More complex bugs are assigned to an explorer agent with a clear symptom and starting context.

bug-investigation — Skill for OpenCode by cruzs85

Install

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.

Any agent

npx skills add cruzs85/opencode-multiagente-local-37-iterations --skill bug-investigation

Clone the repo

git clone --depth 1 https://github.com/cruzs85/opencode-multiagente-local-37-iterations

Made for: OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cruzs85/opencode-multiagente-local-37-iterations/bug-investigation/github.svg)](https://agentmods.dev/skills/cruzs85/opencode-multiagente-local-37-iterations/bug-investigation)

Your own site

<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.

Your own site · 80×15

<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>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 635 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.5	$0.00000	$0.00254
Sonnet 5.5	$0.00000	$0.00127
Haiku 4.5	$0.00000	$0.00064

Measured 2mo ago against content hash 288a4c863d88, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

configuraciones/configuracion-14(multi-agente)/.opencode/skills/bug-investigation/SKILL.md · 66 lines

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

Changes

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.

2mo ago First seen · 66 lines · 0 tokens per session scan A 288a4c863d88

Subscribe to this mod's changes

bug-investigation is a skill published in the GitHub repository cruzs85/opencode-multiagente-local-37-iterations (5 stars, last pushed 3mo 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.

Debugging

bug-investigation next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
bug-investigationcruzs85/opencode-multiagente-local-37-iterations	Skill	5	3mo ago	MIT	A	0	OpenCode
systematic-debuggingopen-metadata/OpenMetadata	Skill	16k	today	Apache-2.0	A	37	Claude Code
log-error-digestzebbern/claude-code-guide	Skill	4.7k	3d ago	MIT	A	71	Claude Code, Codex
incident-response-incident-responsermyndharis/antigravity-skills	Skill	2.0k	2d ago	MIT	A	36	Claude Code, Codex
cwv-optimizeradobe/skills	Skill	322	today	Apache-2.0	A	112	Claude Code
ci-fixersipyourdrink-ltd/bernstein	Skill	1.2k	today	Apache-2.0	A	15	Claude Code, Codex
diagnosing-missing-recordingsPostHog/posthog	Skill	41k	today	none	A	76	Claude Code, Codex