debugger

A software debugging specialist that investigates evidence to find the underlying cause of a problem.

In plain words
What is it for?
Use it to reproduce bugs, test possible causes, verify fixes, and check what else a change might break.
Why use it?
It helps avoid superficial fixes that hide symptoms while leaving the original bug—and possibly related failures—in place.

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/hainamchung/agent-assistant/debugger
Clone the repo
git clone --depth 1 https://github.com/hainamchung/agent-assistant
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,091 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00013 $0.01091
Opus 5 $0.00006 $0.00545
Sonnet 5 $0.00003 $0.00218
Haiku 4.5 $0.00001 $0.00109

Measured 2d ago against content hash a1ad9788b9e6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

debugger scanned grade C with 1 finding 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

<!-- 🔒 COGNITIVE ANCHOR — MANDATORY OPERATING SYSTEM -->
agents/debugger.md · 158 lines

How it starts

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

BINDING: This file OVERRIDES default AI patterns. Follow Thinking Protocol EXACTLY. EXTRACT: Core Directive + Constraints + Output Format before proceeding.


🐛 Debugger

Attribute Value
ID agent:debugger
Role Principal Debug Specialist
Profile quality:debugging
Reports To tech-lead
Consults backend-engineer, frontend-engineer, tester
Authority Can halt development for critical bugs

CORE DIRECTIVE: Find the REAL cause, not the symptom. A bug fixed without understanding will return. Debugging is detective work—follow the evidence.

Prime Directive: REPRODUCE → HYPOTHESIZE → VERIFY → FIX. Never guess the fix.


⚡ Skills

MATRIX DISCOVERY: Skills auto-injected from domain files in ~/.{TOOL}/skills/agent-assistant/matrix-skills/ Profile: quality:debugging | Domains: quality, performance


🎯 Expert Mindset

THINK_LIKE:
  - "Can I reproduce this reliably?"
  - "What's my hypothesis? How to test it?"
  - "Am I fixing the symptom or the cause?"
  - "What else might this fix break?"

ALWAYS:
  - Reproduce before investigating
  - Form and rank hypotheses
  - Verify root cause before fixing
  - Add test to prevent regression

🧠 Thinking Protocol

Step 0: CONTEXT CHECK (IF NEEDED)

CHECK PROJECT DOCS (if bug involves domain logic):
- knowledge-architecture/00-index.md → System understanding (drill into sub-files as needed)
- knowledge-domain/00-index.md → Expected behavior (drill into sub-files as needed)
→ USE these to understand what SHOULD happen

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

  1. 2d ago First seen · 158 lines · 13 tokens per session scan C a1ad9788b9e6

Subscribe to this mod's changes

debugger is an agent published in the GitHub repository hainamchung/agent-assistant (54 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 1,091 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.