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/jsk9999/ai-nexus/debuggit clone --depth 1 https://github.com/JSK9999/ai-nexusWhat 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.00004 | $0.00245 |
| Opus 5 | $0.00002 | $0.00122 |
| Sonnet 5 | $0.00001 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
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.
What it actually says
/debug
When asked to debug an issue:
- Reproduce — Understand the exact steps to trigger the bug
- Read error — Analyze the full error message and stack trace
- Locate — Find the exact line/function where the error originates
- Understand — Read surrounding code to understand intended behavior
- Fix — Make the minimal change to fix the root cause
- Verify — Run tests or demonstrate the fix works
Debugging Checklist
- Read the full error message and stack trace
- Check recent changes (git diff, git log)
- Verify inputs at the failure point
- Check for null/undefined values
- Check for type mismatches
- Check async/await and promise handling
- Check environment variables and config
Rules
- Fix the root cause, not the symptom
- Don't add try/catch to hide errors
- Don't change unrelated code while debugging
- Write a test that reproduces the bug before fixing
- Explain what caused the bug and why the fix works
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 · 32 lines · 4 tokens per session scan A 38286170c3d4
debug is a command published in the GitHub repository JSK9999/ai-nexus (18 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 4 tokens to every session and 245 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
debug
Use when facing any error or unexpected behavior that requires diagnosis before fixing. Do NOT use for quick classification only — use /debug:triage for that.
VibeGuard: Build Fix
Build repair — read build errors, locate root causes, perform minimal repairs, and verify that the build passed.
hatch3r-benchmark
Run and analyze performance benchmarks. Compare results against baselines, identify regressions, and produce performance reports.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.
csm-workledger
Show the surviving work-ledger entries across sessions.
docs-update
/forge:docs-update is the documentation fixer. It compares recently changed source files (from the last 20 commits or 7 days) against documentation files to find staleness, then reads both the outdated doc and the current source code to identify discrepancies -- new functions, changed interfaces, removed features. For…