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.
git clone --depth 1 https://github.com/oxygen-fragment/claude-modularWrote 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/oxygen-fragment/claude-modular/debug-session)<a href="https://agentmods.dev/commands/oxygen-fragment/claude-modular/debug-session"><img src="https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/debug-session/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/oxygen-fragment/claude-modular/debug-session"><img src="https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/debug-session.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.00000 | $0.00603 |
| Opus 5.5 | $0.00000 | $0.00241 |
| Sonnet 5.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 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.
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.
- 1mo 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 (285 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
fix-issue
Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…
ci-sentinel
Daily autonomous classifier for failing PRs across your repos. Runs /ci-debug headless against every open PR with red required checks, posts the verdict as a collapsed PR comment, and appends to a per-repo .sentinel/ledger.jsonl. v1 is propose-don't-apply — NEVER auto-pushes a fix. Use when you're tired of /status…
ci-debug
Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…
deep-audit.skeleton
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects, stack.orm, stack.authmethod Example output.
deadcode.skeleton
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects Example output.
bug-hunter.skeleton
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects Example output.