debugger

debugger is an agent for Claude Code from nyldn/claude-octopus. It costs 17 tokens per session (334 once invoked), scanned A, original, MIT.

A debugging specialist for investigating software failures systematically. It examines errors, traces, recent changes, and likely root causes.

In plain words
What is it for?
Use it to investigate crashes, failing or flaky tests, race conditions, memory problems, deadlocks, dependency issues, and production incidents when explicitly started in an Octopus workflow.
Why use it?
It helps separate the real cause of a bug from its visible symptoms and checks that a fix actually works.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Part of the octo plugin — 70 skills, 108 commands, 10 agents, 18 hooks shipped together

Good fit Use it to investigate crashes, failing or flaky tests, race conditions, memory problems, deadlocks, dependency issues, and production incidents when explicitly started in an Octopus workflow.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/nyldn/claude-octopus/debugger
About the project

Claude Octopus is an orchestration project that sends research, design, and coding tasks to Claude Code and other AI model providers so their results can be compared. Developers use it for multi-model work, disagreement detection, reviews, persistent context, and an optional workflow that moves from discovery through delivery. The catalogue entries are its commands, skills, agents, instructions, hooks, plugins, and settings.

nyldn/claude-octopus · 4,265 stars · on GitHub · reddit.com

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/nyldn/claude-octopus

Made for: Claude Code.

Or install octo, the plugin that ships this one along with the rest of its 70 skills, 108 commands, 10 agents, 18 hooks.

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 debugger

README.md
[![agentmods](https://agentmods.dev/badge/agents/nyldn/claude-octopus/debugger/github.svg)](https://agentmods.dev/agents/nyldn/claude-octopus/debugger)
Your own site
<a href="https://agentmods.dev/agents/nyldn/claude-octopus/debugger"><img src="https://agentmods.dev/badge/agents/nyldn/claude-octopus/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.

agentmods 80×15 button for debugger

Your own site · 80×15
<a href="https://agentmods.dev/agents/nyldn/claude-octopus/debugger"><img src="https://agentmods.dev/badge/agents/nyldn/claude-octopus/debugger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 334 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.00017 $0.00334
Opus 5.5 $0.00007 $0.00134
Sonnet 5.5 $0.00003 $0.00067
Haiku 4.5 $0.00002 $0.00033

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

Security

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

.claude/agents/debugger.md · 60 lines

What it actually says

You are a debugging specialist focused on systematic problem investigation and resolution.

Core Expertise

  • Root Cause Analysis: Scientific method for isolating failures
  • Error Patterns: Stack traces, race conditions, memory issues, deadlocks
  • Tooling: Debuggers, profilers, log analysis, network inspection
  • Test Failures: Flaky tests, environment issues, dependency problems
  • Production Issues: Log correlation, distributed tracing, incident response

Behavioral Traits

  • Forms hypotheses before making changes
  • Isolates variables systematically
  • Reads error messages and stack traces carefully
  • Checks recent changes and git history for clues
  • Validates fixes with reproducible test cases

Response Approach

  1. Reproduce the issue reliably
  2. Read error output and stack traces carefully
  3. Form hypothesis about root cause
  4. Isolate the failing component
  5. Fix the root cause (not symptoms)
  6. Verify fix and add regression test

Output Contract

Return status: COMPLETE | BLOCKED | PARTIAL

COMPLETE

  • Root Cause (mandatory)
  • Fix Applied
  • Regression Test Added
  • Verification Results

BLOCKED

  • Blocker Description
  • What Was Attempted

PARTIAL

  • Completed Sections
  • Remaining Work
  • Confidence: [0-100]
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 · 60 lines · 17 tokens per session scan A ec3485e91f00

Subscribe to this mod's changes

debugger is an agent published in the GitHub repository nyldn/claude-octopus (4,265 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 334 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-08-30.

Related

Other agents, from other repositories

soleur-engineering-review-performance-oracle

Use this agent when you need to analyze code for performance issues, optimize algorithms, identify bottlenecks, or ensure scalability. This includes reviewing database queries, memory usage, caching strategies, and overall system performance. The agent should be invoked after implementing features or when performance…

jikig-ai/soleur · 65 tokens

soleur-engineering-review-legacy-code-expert

Use this agent when you need to safely modify legacy code that lacks tests. It applies Michael Feathers' dependency-breaking techniques from "Working Effectively with Legacy Code" to identify seams, plan characterization tests, and recommend safe transformation paths.

jikig-ai/soleur · 58 tokens

quality-fixer

Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.

shinpr/claude-code-workflows · 44 tokens

doctrine-performance-optimizer

Read-only performance audit of Doctrine usage: N+1 queries, fetch modes, batch processing, missing indexes, and caching opportunities. Use proactively after adding entities, relations, repository queries, or when a page/endpoint is reported slow.

dev-toolings/superpowers-symfony · 53 tokens

evolve-type-safety-audit

Type-design skeptic for the Evolve Loop (Evaluate archetype). The advisor INSERTS this phase after Build — on refactor cycles and on any large diff — to hunt type escape hatches (any / interface{} / unchecked casts / unsafe assertions) and boundaries with no encoded invariant, and BLOCKS when a weak type lets through…

mickeyyaya/evolve-loop · 84 tokens

architect

Deep technical work. Use for complex implementation, deep debugging, cross-module reasoning, architecture review, and risky or security-sensitive changes (auth, billing, migrations, concurrency, caching, data consistency, public APIs). Also reviews work from cheaper agents for hidden flaws.

realgarit/fable-baton · 54 tokens