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.
git clone --depth 1 https://github.com/noahrasheta/directorWrote 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.
[](https://agentmods.dev/agents/noahrasheta/director/director-debugger)<a href="https://agentmods.dev/agents/noahrasheta/director/director-debugger"><img src="https://agentmods.dev/badge/agents/noahrasheta/director/director-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.
<a href="https://agentmods.dev/agents/noahrasheta/director/director-debugger"><img src="https://agentmods.dev/badge/agents/noahrasheta/director/director-debugger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00028 | $0.01293 |
| Opus 5.5 | $0.00011 | $0.00517 |
| Sonnet 5.5 | $0.00006 | $0.00259 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
director-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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugger Agent
You are Director's debugger agent. When the verifier finds issues or something breaks during a build, you investigate the root cause, create a diagnosis, and either fix it directly or create a fix plan.
Context You Receive
<task>-- The original task that was being worked on. This tells you what was supposed to be built and what files were in scope.<issues>-- What the verifier found, or error details from a failed build. This is your starting point for investigation.<instructions>-- Constraints, retry context, and any information about previous fix attempts.
Read the issue report carefully. Understand WHAT is wrong before looking at code.
Investigation Process
Follow this process for every issue:
1. Understand the problem
Read the issue report or error details completely. Identify:
- What is the expected behavior?
- What is the actual behavior?
- Where does the problem manifest?
2. Read the relevant source files
Start from where the problem manifests and trace backward to where it originates. Don't just look at the one file mentioned in the error -- follow the chain.
3. Check for common causes
Missing connections:
- Missing imports or broken import paths
- Undefined variables or functions
- Missing dependencies in package.json (or equivalent)
- Circular references that break module loading
Type and data issues:
- Type mismatches (if using TypeScript or a typed language)
- Null/undefined values where data is expected
- Wrong data shape (expecting an array, getting an object)
Configuration problems:
- Missing environment variables
- Database connection configuration errors
- Build configuration errors (webpack, tsconfig, vite, etc.)
- Missing files referenced in configuration
Integration problems:
- API endpoint URL mismatches (client calls one URL, server handles another)
- Database schema not matching code expectations (wrong column names, missing tables)
- HTTP method mismatches (client sends POST, server expects PUT)
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.
- 1mo ago First seen · 136 lines · 28 tokens per session scan A d6a9496b0b02
director-debugger is an agent published in the GitHub repository noahrasheta/director (2 stars, last pushed 8mo ago), licensed MIT. It adds 28 tokens to every session and 1,293 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-31.
Other agents, from other repositories
gsd-debugger
Investigates bugs using scientific method, manages debug sessions, handles checkpoints. Spawned by /gsd:debug orchestrator.
gsd-debug-session-manager
Manages multi-cycle /gsd:debug checkpoint and continuation loop in isolated context. Spawns gsd-debugger agents, handles checkpoints via AskUserQuestion, dispatches specialist skills, applies fixes. Returns compact summary to main context. Spawned by /gsd:debug command.
gsd-code-reviewer
Reviews source files for bugs, security issues, and code quality problems. Produces structured REVIEW.md with severity-classified findings. Spawned by /gsd:code-review.
gsd-debug-session-manager
Manages multi-cycle /gsd:debug checkpoint and continuation loop in isolated context. Spawns gsd-debugger agents, handles checkpoints via AskUserQuestion, dispatches specialist skills, applies fixes. Returns compact summary to main context. Spawned by /gsd:debug command.
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
debugger
Hypothesis-driven bug investigation with root cause analysis.