debug-status

A status command for checking whether debug mode is enabled in an agentdev project. It reads the project's debug configuration and reports the debug level and recent session files.

In plain words
What is it for?
Use it to verify debug settings, inspect the configuration path, see when it was created, and review recent debug sessions.
Why use it?
It avoids manually locating configuration and session files when diagnosing whether debugging is active.

Command

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-status
Clone the repo
git clone --depth 1 https://github.com/MadAppGang/claude-code
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 878 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 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.00027 $0.00878
Opus 5 $0.00014 $0.00439
Sonnet 5 $0.00005 $0.00176
Haiku 4.5 $0.00003 $0.00088

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

Security

Grade B, and why

debug-status scanned grade B 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.

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
plugins/agentdev/commands/debug-status.md · 131 lines

How it starts

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

Debug Mode Status

Check the current status of agentdev debug mode by reading the per-project configuration file.

Instructions

  1. Check config file at .claude/agentdev-debug.json
  2. Check debug directory and recent session files
  3. Display status summary

Implementation

Execute the following to gather status information:

echo "=== Debug Mode Status ==="
echo ""

# Determine effective debug status
CONFIG_ENABLED="false"
CONFIG_LEVEL="standard"

# Check config file
if [ -f ".claude/agentdev-debug.json" ]; then
  echo "Config File: $(pwd)/.claude/agentdev-debug.json"
  if command -v jq &> /dev/null; then
    CONFIG_ENABLED=$(jq -r '.enabled // false' .claude/agentdev-debug.json)
    CONFIG_LEVEL=$(jq -r '.level // "standard"' .claude/agentdev-debug.json)
    echo "  enabled: $CONFIG_ENABLED"
    echo "  level: $CONFIG_LEVEL"
    CREATED=$(jq -r '.created_at // "unknown"' .claude/agentdev-debug.json)
    echo "  created_at: $CREATED"
  else
    echo "  (install jq for detailed config parsing)"
    cat .claude/agentdev-debug.json
  fi
else
  echo "Config File: NOT FOUND"
  echo "  (Run /agentdev:debug-enable to create)"
fi

echo ""

# Determine effective status
echo "Status:"
if [ "$CONFIG_ENABLED" = "true" ]; then
  echo "  Debug Mode: ENABLED"
  echo "  Level: $CONFIG_LEVEL"
else
  echo "  Debug Mode: DISABLED"
fi

echo ""

# Check debug directory
if [ -d "claude-code-session-debug" ]; then
  echo "Debug Directory: EXISTS"
  echo "  Path: $(pwd)/claude-code-session-debug/"
  echo ""
  echo "Recent Session Files (last 5):"
  ls -lt claude-code-session-debug/*.jsonl 2>/dev/null | head -5 || echo "  No debug files found"
  echo ""
  FILE_COUNT=$(ls claude-code-session-debug/*.jsonl 2>/dev/null | wc -l | tr -d ' ')
  DIR_SIZE=$(du -sh claude-code-session-debug 2>/dev/null | cut -f1 || echo '0')
  echo "Total Files: $FILE_COUNT"
  echo "Total Size: $DIR_SIZE"
else
  echo "Debug Directory: NOT FOUND"
  echo "  (Will be created when debug mode is first used)"
fi

Read the full file on GitHub · 131 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 · 131 lines · 27 tokens per session scan B 11b1541227da

Subscribe to this mod's changes

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