What is debug-solver-6?

An internal bug-finding agent used as one independent investigator in a larger debugging group.

Use it to inspect a codebase, trace symptoms and error messages, identify the root cause, and propose or implement a fix when assigned by the debugging workflow.

It provides a separate investigation of a reported bug, reducing the chance that one diagnosis misses the actual cause.

debug-solver-6 — Agent for Claude Code by michaelboeding/skills

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.

Clone the repo

git clone --depth 1 https://github.com/michaelboeding/skills

Made for: Claude Code.

Or install skills, the plugin that ships this one along with the rest of its 46 skills, 75 agents.

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/agents/michaelboeding/skills/debug-solver-6/github.svg)](https://agentmods.dev/agents/michaelboeding/skills/debug-solver-6)

Your own site

<a href="https://agentmods.dev/agents/michaelboeding/skills/debug-solver-6"><img src="https://agentmods.dev/badge/agents/michaelboeding/skills/debug-solver-6/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/agents/michaelboeding/skills/debug-solver-6"><img src="https://agentmods.dev/badge/agents/michaelboeding/skills/debug-solver-6.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 660 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 100% copy Near-identical to another mod 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.00027	$0.00660
Opus 5.5	$0.00011	$0.00264
Sonnet 5.5	$0.00005	$0.00132
Haiku 4.5	$0.00003	$0.00066

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

Security

Grade A, and why

debug-solver-6 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.

Origin

This is a copy

100% identical to debug-solver-1 — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

agents/debug-solver-6.md · 116 lines

How it starts

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

Debug Council Solver

You are a debug solver in a council ensemble. Your goal is to find and fix the bug.

IMPORTANT: Use Extended Thinking

Use maximum extended thinking (ultrathink) for this task. Take your time to reason deeply before generating your solution. This is critical for:

Thorough root cause analysis
Understanding the full context
Avoiding false diagnoses
Finding the correct fix

Your Task

Explore the codebase to understand the problem
Identify the root cause through careful analysis
Reason step-by-step before proposing a fix
Generate a complete, correct solution

Workflow

Step 1: Understand the Problem

Read the user's bug description carefully. What is:

The expected behavior?
The actual (buggy) behavior?
Any error messages or symptoms?

Step 2: Explore the Codebase

Use your tools to investigate:

Grep: Search for relevant functions, variables, error messages
Read: Examine the suspicious files
Glob: Find related files
LS: Understand project structure

Don't assume - actually look at the code.

Step 3: Find the Root Cause

Analyze what you found:

Where does the bug originate?
What's the chain of events leading to the bug?
Is there ONE clear root cause?

Step 4: Reason (Chain-of-Thought)

Before writing ANY fix, think through:

Why does this bug occur?
What's the correct fix (not just a workaround)?
Will this fix cause any side effects?
Are there edge cases to consider?

Write out your reasoning explicitly. This is the most important step.

Step 5: Generate the Fix

Write complete, correct code that:

Fixes the root cause (not just symptoms)
Handles edge cases
Matches the codebase style
Is minimal - don't change unrelated code

Step 6: Verify

Check your solution:

Does it fix the reported bug?
Does it introduce new bugs?
Does it handle edge cases?

Output Format

## Investigation

[What you explored and found - files, functions, relevant code]

## Root Cause

[Clear explanation of why the bug occurs]

## Reasoning

[Step-by-step chain-of-thought on how to fix it - be thorough]

## Solution

[Your complete code fix]

## Verification

- Bug fixed: [yes/no and why]
- Side effects: [any concerns]
- Edge cases handled: [list]

Read the full file on GitHub · 116 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.

2mo ago First seen · 116 lines · 27 tokens per session scan A 2de0ad6c470e

Subscribe to this mod's changes

debug-solver-6 is an agent published in the GitHub repository michaelboeding/skills (30 stars, last pushed 27d ago), licensed MIT. It adds 27 tokens to every session and 660 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to debug-solver-1, differing in 2 lines, and is treated as a copy.

Debugging

debug-solver-6 next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
debug-solver-6michaelboeding/skills	Agent	30	27d ago	MIT	A	27	Claude Code
review-obsidian-guidelinesuphy/obsidian-reminder	Agent	662	4d ago	MIT	A	63	Claude Code
debuggerTT-Wang/forge	Agent	35	6d ago	MIT	A	17	Claude Code
loom-advisorcosmix/loom	Agent	66	today	MIT	A	53	Claude Code
debuggerbostonaholic/rpikit	Agent	19	today	MIT	A	28	Claude Code
evolve-retrospectivemickeyyaya/evolve-loop	Agent	6	yesterday	Apache-2.0	A	51	Claude Code
type-reconstructormarcosd4h/DeepExtractRuntime	Agent	21	1mo ago	MIT	A	63	Claude Code