debug-toolbar: Command for Claude Code

.claude/commands/explore.md

explore is a command for Claude Code from JacobCoffee/debug-toolbar. It costs 9 tokens per session (695 once invoked), scanned A, original, MIT.

A codebase exploration workflow for learning a project's architecture and existing patterns. It uses an exploration helper to inspect the code and summarise important areas and classes.

In plain words
What is it for?
Use it to map modules, find key classes, and investigate how a feature is structured. It is useful during planning or when taking over an unfamiliar project.
Why use it?
It helps you understand unfamiliar code before making changes, reducing the chance of overlooking related components or established conventions.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is JacobCoffee/debug-toolbar's own configuration. It tells Claude Code how to work on debug-toolbar itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything debug-toolbar configures →

Reuse

Borrowing it

Nothing to install: this file belongs to JacobCoffee/debug-toolbar. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/JacobCoffee/debug-toolbar/main/.claude/commands/explore.md
Clone the repo
git clone --depth 1 https://github.com/JacobCoffee/debug-toolbar

Made for: Claude Code.

Wrote 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.

agentmods badge for explore

README.md
[![agentmods](https://agentmods.dev/badge/commands/jacobcoffee/debug-toolbar/explore.svg)](https://agentmods.dev/commands/jacobcoffee/debug-toolbar/explore)
Your own site
<a href="https://agentmods.dev/commands/jacobcoffee/debug-toolbar/explore"><img src="https://agentmods.dev/badge/commands/jacobcoffee/debug-toolbar/explore.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 695 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00009 $0.00695
Opus 5 $0.00005 $0.00347
Sonnet 5 $0.00002 $0.00139
Haiku 4.5 $0.00001 $0.00069

Measured 2d ago against content hash 3a7e428bc65e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

explore 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.

.claude/commands/explore.md · 123 lines

How it starts

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

Codebase Exploration

You are exploring: $ARGUMENTS

Exploration Strategy

Use the Task tool with subagent_type=Explore for thorough codebase exploration.

Quick Reference

Architecture Overview

src/debug_toolbar/
├── __init__.py              # Public API exports
├── core/                    # Framework-agnostic core
│   ├── panel.py             # Panel ABC
│   ├── toolbar.py           # DebugToolbar manager
│   ├── config.py            # DebugToolbarConfig
│   ├── context.py           # RequestContext
│   ├── storage.py           # ToolbarStorage
│   └── panels/              # Built-in panels
├── litestar/                # Litestar integration
│   ├── plugin.py            # DebugToolbarPlugin
│   ├── middleware.py        # ASGI middleware
│   ├── config.py            # LitestarDebugToolbarConfig
│   ├── routes/              # API routes
│   └── panels/              # Litestar-specific panels
└── extras/                  # Optional integrations
    └── advanced_alchemy/    # SQLAlchemy/AA integration

Key Classes

Class Location Purpose
Panel core/panel.py Abstract base for all panels
DebugToolbar core/toolbar.py Main toolbar manager
DebugToolbarConfig core/config.py Core configuration
RequestContext core/context.py Request-scoped data
DebugToolbarPlugin litestar/plugin.py Litestar integration

Common Exploration Tasks

Find all panels:

grep -r "class.*Panel" src/debug_toolbar/

Find all configs:

grep -r "class.*Config" src/debug_toolbar/

Find all tests for a module:

find tests/ -name "test_*.py" | xargs grep -l "{module_name}"

Find usage of a class:

grep -r "ClassName" src/ tests/

Deep Exploration

For complex exploration, use:

Task(
    subagent_type="Explore",
    prompt="Explore {topic} in the codebase. Find:
    1. All related files
    2. Key patterns used
    3. How components connect
    4. Testing approaches"
)

Read the full file on GitHub · 123 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 · 123 lines · 9 tokens per session scan A 3a7e428bc65e

Subscribe to this mod's changes

explore is a command published in the GitHub repository JacobCoffee/debug-toolbar (7 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 695 once invoked, about $0.0000 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-09-04.