bug-investigator

bug-investigator is a skill for Claude Code, Codex from sequenzia/agent-alchemy. It costs 33 tokens per session (1,038 once invoked), scanned A, original, MIT.

A diagnostic investigation tool that tests a specific theory about why a bug happens and reports the evidence without changing the code.

In plain words
What is it for?
It is for tracing program execution, running targeted tests, checking Git history, and investigating bug hypotheses.
Why use it?
It helps separate confirmed causes from guesses before someone attempts a fix.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for tracing program execution, running targeted tests, checking Git history, and investigating bug hypotheses.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sequenzia/agent-alchemy/bug-investigator
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 sequenzia/agent-alchemy --skill bug-investigator
Clone the repo
git clone --depth 1 https://github.com/sequenzia/agent-alchemy

Made for: Claude Code, Codex.

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.

agentmods badge for bug-investigator

README.md
[![agentmods](https://agentmods.dev/badge/skills/sequenzia/agent-alchemy/bug-investigator/github.svg)](https://agentmods.dev/skills/sequenzia/agent-alchemy/bug-investigator)
Your own site
<a href="https://agentmods.dev/skills/sequenzia/agent-alchemy/bug-investigator"><img src="https://agentmods.dev/badge/skills/sequenzia/agent-alchemy/bug-investigator/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.

agentmods 80×15 button for bug-investigator

Your own site · 80×15
<a href="https://agentmods.dev/skills/sequenzia/agent-alchemy/bug-investigator"><img src="https://agentmods.dev/badge/skills/sequenzia/agent-alchemy/bug-investigator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,038 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.01038
Opus 5.5 $0.00013 $0.00415
Sonnet 5.5 $0.00007 $0.00208
Haiku 4.5 $0.00003 $0.00104

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

Security

Grade A, and why

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

ported/20260304-102613/dev-tools/skills/bug-investigator/SKILL.md · 161 lines

How it starts

The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Bug Investigator

When invoked, perform the following diagnostic investigation tasks: test a specific hypothesis about a bug by gathering evidence. Do NOT fix bugs — investigate them and report findings.

Prerequisites

No external skills are required. This skill operates independently.

Mission

Given a hypothesis about a bug's root cause:

  1. Design and execute diagnostic tests to confirm or reject the hypothesis
  2. Gather concrete evidence (code, output, history)
  3. Report structured findings back to the caller

Investigation Techniques

Code Tracing

Follow the execution path to understand what actually happens:

  • Read the relevant source files and trace data flow
  • Identify where actual behavior diverges from expected behavior
  • Map function call chains from entry point to error site
  • Check for implicit type conversions, default values, or fallback behavior

Diagnostic Testing

Run targeted commands to observe behavior:

# Run the specific failing test in isolation
pytest -xvs path/to/test_file.py::test_name

# Run with verbose/debug output
NODE_DEBUG=module node script.js

# Check exit codes
command; echo "Exit code: $?"

Git History Analysis

Use version control to understand when and why:

# Who last changed the relevant code
git blame path/to/file.py -L start,end

# When was this area last modified
git log --oneline -10 -- path/to/file.py

# What changed in the relevant area recently
git log -p --follow -S "function_name" -- path/to/file.py

# Find the commit that introduced the bug
git bisect start
git bisect bad HEAD
git bisect good <known-good-commit>

State and Configuration Checks

Verify the runtime environment:

# Check environment variables
env | grep RELEVANT_PREFIX

# Verify file permissions
ls -la path/to/file

# Check running processes
ps aux | grep process_name

# Verify dependency versions
pip show package_name
npm list package_name

Data Inspection

Examine actual vs expected data:

  • Read configuration files that affect the code path
  • Check database schemas or data fixtures
  • Verify API response formats match expectations
  • Compare test fixtures against production-like data

Read the full file on GitHub · 161 lines

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.

  1. 1mo ago First seen · 161 lines · 33 tokens per session scan A 7bc9c51d716a

Subscribe to this mod's changes

bug-investigator is a skill published in the GitHub repository sequenzia/agent-alchemy (45 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 1,038 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-03.

Related

Other skills, from other repositories

debugger

Systematic debugging method: 5-step root-cause analysis (capture, isolate, hypothesize, investigate, fix & verify) plus common bug-pattern reference. Use when errors, exceptions, test failures, or unexpected behavior appear. Loaded automatically by the debugger agent.

claude-world/director-mode-lite · 56 tokens

mcp-check

Validate MCP configuration and suggest improvements. Use when MCP servers fail to load, after editing .mcp.json, or when the user runs /mcp-check.

claude-world/director-mode-lite · 36 tokens

debug

Systematic bug investigation with a five-phase framework: reproduce, narrow, diagnose, fix, verify. Supports automated regression bisect via --regression flag. Produces a structured debug report with root cause analysis, regression test, and CQ/Q self-evaluations.

greglas75/zuvo · 55 tokens

project-health-check

Audit project health across 7 dimensions (documentation, test coverage, security, code quality, dependencies, database, build/deploy) producing a scored report with prioritized fixes. Use for periodic checkups, before releases, or when the user runs /project-health-check.

claude-world/director-mode-lite · 57 tokens

ccc-systematic-debugging

Root-cause debugging under one law: no fix without a confirmed root cause. Reproduce, compare, hypothesize, then fix once with a failing test first. Use when investigating a bug, a failing or flaky test, or an error of unknown cause.

KevinZai/commander · 58 tokens

dekko-verify

Sanity-check a suspiciously low or zero call-graph result from dekko (getcallers, getcallees, findusages, impactedtests, unused) before concluding "no callers" or "dead code," or a heritage/throws-provenance result (query supertypes, query subtypes, query throws) that labels something (external) when you expect it to…

aahlijia/dekko · 151 tokens