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/JSK9999/ai-nexusWrote 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/jsk9999/ai-nexus/debug)<a href="https://agentmods.dev/commands/jsk9999/ai-nexus/debug"><img src="https://agentmods.dev/badge/commands/jsk9999/ai-nexus/debug/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/jsk9999/ai-nexus/debug"><img src="https://agentmods.dev/badge/commands/jsk9999/ai-nexus/debug.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.00004 | $0.00245 |
| Opus 5.5 | $0.00002 | $0.00098 |
| Sonnet 5.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 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
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.
- 1mo ago First seen · 32 lines · 4 tokens per session scan A 38286170c3d4
debug is a command published in the GitHub repository JSK9999/ai-nexus (19 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 4 tokens to every session and 245 once invoked, about $0.0000 per session on Opus 5.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.
fix-issues
Diagnose, reproduce, then fix reproducible open GitHub issues in parallel: one clean worktree/issue; symlink build artifacts to avoid rebuilds.
investigate
Establish the proven causal chain for the target — from the observed symptom to the root cause that actually explains it — and write a report a fixer or planner can act on without repeating your work. You change nothing and fix nothing: the repository must be exactly as you found it when you finish. No one watches the…
maintainer-review-error-handling
Review the PR for error-handling correctness — surfaced errors, no silent swallows, consistent error patterns (Pi-tuned).
review-errors
Find either defect: a real failure crosses the changed code and becomes indistinguishable from success to the caller, operator, or user who must react; or it escapes its owning item and aborts independent work. Not every error needs logging; recovery is correct when the contract permits it and the right owner can…
classify-red
The project's gate ran and at least one check failed. $ARTIFACTSDIR/validation.md is the record: every check that ran, its group, its exit status, each failing check's output tail, and the path of each check's full output log. Decide why the failed checks failed, judging every one the record names. You fix nothing and…