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/boparaiamrit/skills-by-amritWrote 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/boparaiamrit/skills-by-amrit/debug)<a href="https://agentmods.dev/commands/boparaiamrit/skills-by-amrit/debug"><img src="https://agentmods.dev/badge/commands/boparaiamrit/skills-by-amrit/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.1 | $0.00011 | $0.00367 |
| Opus 5 | $0.00005 | $0.00183 |
| Sonnet 5 | $0.00002 | $0.00073 |
| Haiku 4.5 | $0.00001 | $0.00037 |
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 8d 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 — Systematic Debugging
Diagnose and fix an issue using structured problem-solving.
Instructions
-
Reproduce — Understand the issue from
$ARGUMENTS:- What is the expected behavior?
- What is the actual behavior?
- When did it start? (check recent commits with
git log --oneline -20)
-
Isolate — Narrow down the root cause:
- Search for related error messages in the codebase
- Trace the execution path from entry point to failure
- Check recent changes:
git log --diff-filter=M --name-only -10 - Look for obvious culprits: typos, missing imports, wrong variable names
-
Diagnose — Identify the root cause:
- Don't fix symptoms — find the actual cause
- Check if the issue exists in tests (and if tests are passing incorrectly)
- Verify assumptions about data shapes, API responses, and state
-
Fix — Apply the minimal correct fix:
- Change the fewest lines possible
- Don't refactor while debugging
- Add a comment explaining WHY this was the fix if non-obvious
-
Verify — Confirm the fix works:
- Run the relevant tests
- Manually verify the fix addresses the original issue
- Check for regression: did the fix break anything else?
-
Prevent — Add safeguards:
- Write a test that would have caught this bug
- Add error handling if the root cause was an unhandled edge case
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.
- 8d ago First seen · 43 lines · 11 tokens per session scan A de92f4a3e1a2
debug is a command published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 367 once invoked, about $0.0001 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-31.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.