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.
npx agentmods add commands/oxygen-fragment/claude-modular/debug-sessiongit clone --depth 1 https://github.com/oxygen-fragment/claude-modularWhat 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.00000 | $0.00603 |
| Opus 5 | $0.00000 | $0.00302 |
| Sonnet 5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
debug-session 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 3d 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.
What it actually says
Debug Session Command
2. **Environment Investigation**
- Check environment variables and configuration
- Verify dependency versions
- Analyze system resources and limits
- Review recent changes and deployments
3. **Code Analysis**
- Trace code execution paths
- Identify potential null pointer/undefined access
- Check boundary conditions and edge cases
- Review error handling and logging
4. **Data Analysis**
- Examine input data and parameters
- Validate data types and formats
- Check database state and queries
- Analyze network requests and responses
5. **Root Cause Identification**
- Isolate the minimal reproduction case
- Identify the exact failure point
- Determine underlying cause
- Assess impact and affected components
6. **Resolution Strategy**
- Develop fix implementation plan
- Create test cases for the issue
- Implement monitoring and prevention
- Document lessons learned
# Interactive debugging:
# - Error analysis
# - Log investigation
# - Code tracing
# - Solution implementation
```
```bash
# Debug specific error with context
/dev:debug-session --error="NullPointerException" --context="user-login"
# Focused debugging:
# - Specific error type analysis
# - Contextual code review
# - Targeted fix implementation
```
```bash
# Debug performance issue
/dev:debug-session --type=performance --metric=response-time
# Performance debugging:
# - Profiling analysis
# - Bottleneck identification
# - Optimization recommendations
# - Performance testing
```
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.
- 3d ago First seen · 97 lines · 0 tokens per session scan A 370f5b86e1ab
debug-session is a command published in the GitHub repository oxygen-fragment/claude-modular (283 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 603 tokens. 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-08-30.
Other commands, from other repositories
paul:help
Show available PAUL commands and usage guide.
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
paul:verify
Guide manual user acceptance testing of recently built features.
auto
Intent-classified router, the front door to OrchestKit and the DEFAULT entry point for any goal-shaped request. Classifies a plain-English goal and routes it to the right specialist skill. Routing is never overhead, so use it even when the target skill seems obvious; skip only when already executing inside another…
design-to-code
Mockup-to-component pipeline using Google Stitch, 21st.dev, and Storybook MCP. Accepts a screenshot, a description, or a URL and produces production-ready React components, checking existing Storybook components before generating anything new. Use when implementing UI from a mockup or screenshot. To call the MCP tool…
dream
Nightly memory consolidation — prunes stale entries, merges duplicates, resolves contradictions, rebuilds MEMORY.md index. Use when memory files have accumulated over many sessions and need cleanup. Do NOT use for storing new decisions (use remember) or searching memory (use memory).