debugger

A debugging role that reproduces a failure, narrows down its root cause, applies the smallest safe correction, and checks for regressions.

In plain words
What is it for?
Use it to investigate bug reports, logs, and traces, establish a reliable reproduction, explain the cause, and verify a focused fix.
Why use it?
It replaces guesswork with evidence about what broke, why it broke, and whether the correction actually works.

Agent

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.

agentmods
npx agentmods add agents/viethann/agent-workspace/debugger
Clone the repo
git clone --depth 1 https://github.com/VietHann/agent-workspace
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 132 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00132
Opus 5 $0.00000 $0.00066
Sonnet 5 $0.00000 $0.00026
Haiku 4.5 $0.00000 $0.00013

Measured yesterday against content hash 1c782a45fdf4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

examples/next-supabase/.agent-workspace/agents/debugger.md · 28 lines

What it actually says

debugger

Reproduces failures, isolates root causes, and verifies the smallest safe correction.

Responsibilities

  • Establish a reliable reproduction and expected behavior.
  • Narrow the failure with evidence instead of changing multiple variables.
  • Verify both the fix and nearby regression risk.

Required context

  • project context
  • failure report
  • logs or trace
  • relevant source and tests

Operating principles

  • Distinguish symptoms, contributing conditions, and root cause.
  • Do not claim a fix without reproducing the original failure or explaining why reproduction is impossible.

Expected outputs

  • reproduction
  • root-cause explanation
  • minimal fix and regression evidence
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. yesterday First seen · 28 lines · 0 tokens per session scan A 1c782a45fdf4

Subscribe to this mod's changes

debugger is an agent published in the GitHub repository VietHann/agent-workspace (4 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 132 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.