What is debug-disable?

A command that turns off debug logging for agentdev sessions. Debug logging records tool calls and requests sent between agents.

Use it when you want to disable agentdev debugging in a project and update its local configuration file.

It stops new session activity from being recorded in the project’s debug configuration, reducing extra diagnostic data when it is no longer needed.

debug-disable — Command by MadAppGang

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 commands/madappgang/claude-code/debug-disable

Clone the repo

git clone --depth 1 https://github.com/MadAppGang/claude-code

Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 586 The whole file, excluding the scripts and references it only reads on demand.

Security scan D 2 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.

Model	Per session	Once invoked
Fable 5	$0.00021	$0.00586
Opus 5	$0.00010	$0.00293
Sonnet 5	$0.00004	$0.00117
Haiku 4.5	$0.00002	$0.00059

Measured yesterday against content hash 6cd3d273d270, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade D, and why

debug-disable scanned grade D with 2 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat .claude/agentdev-debug.json

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf claude-code-session-debug/

plugins/agentdev/commands/debug-disable.md · 88 lines

How it starts

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

Disable Debug Mode

Disable agentdev debug mode by updating the per-project configuration file.

Instructions

Check if config file exists
Update .claude/agentdev-debug.json with enabled: false
Show confirmation

Implementation

Execute the following to disable debug mode:

echo "=== Disabling Debug Mode ==="
echo ""

# Check if config file exists
if [ -f ".claude/agentdev-debug.json" ]; then
  # Update enabled to false using jq if available
  if command -v jq &> /dev/null; then
    TIMESTAMP=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
    jq --arg ts "$TIMESTAMP" '.enabled = false | .disabled_at = $ts' .claude/agentdev-debug.json > .claude/agentdev-debug.json.tmp
    mv .claude/agentdev-debug.json.tmp .claude/agentdev-debug.json
    echo "Config updated: $(pwd)/.claude/agentdev-debug.json"
    cat .claude/agentdev-debug.json
  else
    # Fallback: delete and recreate with enabled: false
    TIMESTAMP=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
    cat > .claude/agentdev-debug.json << EOF
{
  "enabled": false,
  "level": "standard",
  "disabled_at": "$TIMESTAMP"
}
EOF
    echo "Config updated: $(pwd)/.claude/agentdev-debug.json"
    cat .claude/agentdev-debug.json
  fi
else
  echo "No config file found at .claude/agentdev-debug.json"
  echo "Debug mode was not enabled."
fi

Response Format

Display the following:

Debug Mode: DISABLED

Config: .claude/agentdev-debug.json
Status: enabled = false

Note: Existing debug files in claude-code-session-debug/ are preserved.

Use /agentdev:debug-status to verify debug mode is disabled.

Alternative: Delete Config File

If you want to completely remove the config file instead of setting enabled: false:

rm -f .claude/agentdev-debug.json
echo "Config file removed."

Cleanup Debug Files

If the user wants to clean up debug files, suggest:

# Remove all debug files
rm -rf claude-code-session-debug/

# Or remove files older than 7 days
find claude-code-session-debug/ -name "*.jsonl" -mtime +7 -delete

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

yesterday First seen · 88 lines · 21 tokens per session scan D 6cd3d273d270

Subscribe to this mod's changes

debug-disable is a command published in the GitHub repository MadAppGang/claude-code (279 stars, last pushed 5mo ago), licensed MIT. It adds 21 tokens to every session and 586 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Debugging

debug-disable

Getting it into your agent

What it costs to keep this loaded

Grade D, and why

Reads agent configuration directoriesmediumAgent snooping

Recursive force deletehighDestructive command

How it starts

Disable Debug Mode

Instructions

Implementation

Response Format

Alternative: Delete Config File

Cleanup Debug Files

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement