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/yousefnabil-soc/claude-apex/debuggit clone --depth 1 https://github.com/YousefNabil-SOC/claude-apexWrote 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/yousefnabil-soc/claude-apex/debug)<a href="https://agentmods.dev/commands/yousefnabil-soc/claude-apex/debug"><img src="https://agentmods.dev/badge/commands/yousefnabil-soc/claude-apex/debug.svg" alt="Measured on agentmods" 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 | $0.00014 | $0.00992 |
| Opus 5 | $0.00007 | $0.00496 |
| Sonnet 5 | $0.00003 | $0.00198 |
| Haiku 4.5 | $0.00001 | $0.00099 |
Grade A, and why
gsd: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 4d 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.
This is a copy
88% identical to gsd:debug — 27 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator role: Gather symptoms, spawn gsd-debugger agent, handle checkpoints, spawn continuations.
Why subagent: Investigation burns context fast (reading files, forming hypotheses, testing). Fresh 200k context per investigation. Main context stays lean for user interaction.
Check for active sessions:
ls .planning/debug/*.md 2>/dev/null | grep -v resolved | head -5
0. Initialize Context
INIT=$(node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" state load)
if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
Extract commit_docs from init JSON. Resolve debugger model:
debugger_model=$(node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" resolve-model gsd-debugger --raw)
1. Check Active Sessions
If active sessions exist AND no $ARGUMENTS:
- List sessions with status, hypothesis, next action
- User picks number to resume OR describes new issue
If $ARGUMENTS provided OR user describes new issue:
- Continue to symptom gathering
2. Gather Symptoms (if new issue)
Use AskUserQuestion for each:
- Expected behavior - What should happen?
- Actual behavior - What happens instead?
- Error messages - Any errors? (paste or describe)
- Timeline - When did this start? Ever worked?
- Reproduction - How do you trigger it?
After all gathered, confirm ready to investigate.
3. Spawn gsd-debugger Agent
Fill prompt and spawn:
<objective>
Investigate issue: {slug}
**Summary:** {trigger}
</objective>
<symptoms>
expected: {expected}
actual: {actual}
errors: {errors}
reproduction: {reproduction}
timeline: {timeline}
</symptoms>
<mode>
symptoms_prefilled: true
goal: find_and_fix
</mode>
<debug_file>
Create: .planning/debug/{slug}.md
</debug_file>
Task(
prompt=filled_prompt,
subagent_type="gsd-debugger",
model="{debugger_model}",
description="Debug {slug}"
)
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.
- 4d ago First seen · 169 lines · 14 tokens per session scan A 78cd1921d5b2
gsd:debug is a command published in the GitHub repository YousefNabil-SOC/claude-apex (2 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 992 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to gsd:debug, differing in 27 lines, and is treated as a copy.
Other commands, from other repositories
grill-me
Run an interactive one-question-at-a-time oral drill for research defence or active-recall study, escalating around weak answers and ending with a study sheet. Use when the user asks to be grilled, quizzed, or prepared for a viva, job talk, seminar, or exam. Not for a written critique; use $devils-advocate or a review…
thoughts_init
Initialize thoughts system for current repository.
hades-validate-memory
Validate every Asphodel memory file and report results.
reflect
After the user triggers this command, run Learning Loop steps 4-8. Two phases: first half (review + organize) completes, then automatically continues to second half (re-analyze + trim + wrap up).
check
Run a quick scan of the memory system's health. For daily use.
recover
Restore memory from your GitHub backup when local memory files are lost or corrupted. Also works for cross-device sync.