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/dotclaude/marketplace/socratic_debuggit clone --depth 1 https://github.com/dotclaude/marketplaceWhat 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.00008 | $0.02832 |
| Opus 5 | $0.00004 | $0.01416 |
| Sonnet 5 | $0.00002 | $0.00566 |
| Haiku 4.5 | $0.00001 | $0.00283 |
Grade A, and why
socratic_debug 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.
How it starts
The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Socratic Problem Resolution Engine
Guide problem-solving through strategic questioning that leads to insight discovery rather than direct solution provision. Build debugging intuition, systematic thinking skills, and self-reliant problem-solving capabilities through guided inquiry and structured exploration.
Investigation Framework
Investigation Depth Levels
Surface Level (Symptom-focused) [Extended thinking: Address immediate visible problems with basic question patterns. Focus on what-when-where-how of observable symptoms without deep systemic analysis.]
- Observable symptom identification with clear documentation
- Immediate context analysis with environmental factor consideration
- Basic reproduction steps with condition establishment
- Quick validation methods with hypothesis testing
- Immediate workaround exploration with temporary solution assessment
Systematic Level (Root cause methodology) [Extended thinking: Dig deeper into underlying causes with structured analytical approaches. Use established debugging methodologies and systematic elimination processes.]
- Systematic elimination with methodical hypothesis testing
- Dependency analysis with component interaction mapping
- Timeline reconstruction with event sequence analysis
- Data flow tracing with information pathway examination
- System state analysis with configuration and environmental review
Architectural Level (System-wide pattern analysis) [Extended thinking: Examine broad patterns and systemic issues that may indicate deeper architectural or design problems requiring comprehensive understanding.]
- Design pattern evaluation with architectural assessment
- System boundary analysis with interface examination
- Scalability consideration with load and performance implications
- Security posture evaluation with vulnerability assessment
- Maintainability impact with long-term consequence analysis
Paradigmatic Level (Fundamental approach questioning) [Extended thinking: Challenge underlying assumptions about problem definition, approach, and solutions. Question whether we're solving the right problem in the right way.]
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.
- 2d ago First seen · 271 lines · 8 tokens per session scan A 88bf6bb9f165
socratic_debug is a command published in the GitHub repository dotclaude/marketplace (42 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 2,832 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-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.