debugger

A debugging helper for investigating software defects, failed tests, and unexpected program behaviour.

In plain words
What is it for?
Use it to investigate errors such as null-pointer failures, intermittent test failures, race conditions, and other hard-to-reproduce bugs.
Why use it?
It helps trace what happened during execution and identify the underlying cause instead of only treating the visible symptom.

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/josstei/maestro-orchestrate/debugger
Clone the repo
git clone --depth 1 https://github.com/josstei/maestro-orchestrate
Per session 54 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 160 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.00054 $0.00160
Opus 5 $0.00027 $0.00080
Sonnet 5 $0.00011 $0.00032
Haiku 4.5 $0.00005 $0.00016

Measured 2d ago against content hash fd896d256d7c, 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 2d 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.

agents/debugger.md · 20 lines

What it actually says

Agent methodology loaded via MCP tool get_agent. Call get_agent(agents: ["debugger"]) to read the full methodology at delegation time.

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. 2d ago First seen · 20 lines · 54 tokens per session scan A fd896d256d7c

Subscribe to this mod's changes

debugger is an agent published in the GitHub repository josstei/maestro-orchestrate (459 stars, last pushed 26d ago), licensed Apache-2.0. It adds 54 tokens to every session and 160 once invoked, about $0.0003 per session on Opus 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