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.
curl -O https://raw.githubusercontent.com/JacobCoffee/debug-toolbar/main/.claude/commands/explore.mdgit clone --depth 1 https://github.com/JacobCoffee/debug-toolbarWrote 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/commands/jacobcoffee/debug-toolbar/explore)<a href="https://agentmods.dev/commands/jacobcoffee/debug-toolbar/explore"><img src="https://agentmods.dev/badge/commands/jacobcoffee/debug-toolbar/explore/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/commands/jacobcoffee/debug-toolbar/explore"><img src="https://agentmods.dev/badge/commands/jacobcoffee/debug-toolbar/explore.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.00009 | $0.00695 |
| Opus 5.5 | $0.00004 | $0.00278 |
| Sonnet 5.5 | $0.00002 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00069 |
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 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 — 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"
)
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 · 123 lines · 9 tokens per session scan A 3a7e428bc65e
explore is a command published in the GitHub repository JacobCoffee/debug-toolbar (8 stars, last pushed 17d ago), licensed MIT. It adds 9 tokens to every session and 695 once invoked, about $0.0000 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-09-04.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
react-native
Command "react-native" from getsentry/toolkit, covering xcode build step (react-native xcode) and important notes.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
fix
Universal debugging and fix application with semantic code analysis.