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 skills/deepank308/hermes-swe-agent/debuggingnpx skills add Deepank308/hermes-swe-agent --skill debugginggit clone --depth 1 https://github.com/Deepank308/hermes-swe-agentWhat 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.00035 | $0.00546 |
| Opus 5 | $0.00017 | $0.00273 |
| Sonnet 5 | $0.00007 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
debugging 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging Workflow
Use this workflow for bug reports, production errors, Sentry issues, and regressions.
Phase 1: Investigate
- Read the ticket for error details, stack traces, Sentry links, and reproduction steps.
- If a Sentry URL is provided: invoke
/debugging-sentry-issuesfor Sentry/Metabase MCP investigation. - If local debugging is needed: invoke
/debug-referencefor Docker environment commands and debugging tips. - Invoke
superpowers:systematic-debuggingand follow its 4-phase methodology:- Root cause analysis: trace the error to its origin.
- Pattern analysis: identify what conditions trigger the bug.
- Hypothesis formation: form a testable theory about the cause.
- Implementation: plan the minimal fix.
Phase 2: Reproduce
- Create a failing test that captures the bug scenario.
- Run the test and verify it fails for the right reason (the actual bug, not a setup issue).
- This serves as the TDD RED phase — the test defines the expected correct behavior.
Phase 3: Fix
- Implement a minimal, targeted fix — only address the root cause.
- Do not refactor surrounding code or fix unrelated issues.
- Run the failing test and verify it now passes (TDD GREEN phase).
Phase 4: Verify
Invoke superpowers:verification-before-completion and follow its methodology:
- Run the broader test suite to check for regressions.
- Run lint on changed JS/TS files.
- If any failures: fix the issue and re-verify (up to 3 attempts).
- Do NOT proceed to Phase 5 until all checks pass with evidence.
Phase 5: Commit & PR
- Stage changed files and commit with a
Fix: <description>message. - Push to the working branch.
- Create a PR with:
- Title. Include Linear Issue identifier (
[ENG-XXXX]: Fix <concise description>). - Description including:
- Root cause analysis.
- What the fix does and why.
- Test results.
- Title. Include Linear Issue identifier (
Phase 6: Summary
Output a summary:
- Root cause of the bug.
- How it was reproduced (test name/description).
- What the fix does.
- Test results (pass counts, no regressions).
- PR link.
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 · 62 lines · 35 tokens per session scan A 76d7ed3ee946
debugging is a skill published in the GitHub repository Deepank308/hermes-swe-agent (11 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 546 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…