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 skills add Deepank308/hermes-swe-agent --skill debugginggit clone --depth 1 https://github.com/Deepank308/hermes-swe-agentWrote 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/skills/deepank308/hermes-swe-agent/debugging)<a href="https://agentmods.dev/skills/deepank308/hermes-swe-agent/debugging"><img src="https://agentmods.dev/badge/skills/deepank308/hermes-swe-agent/debugging/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/skills/deepank308/hermes-swe-agent/debugging"><img src="https://agentmods.dev/badge/skills/deepank308/hermes-swe-agent/debugging.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.00035 | $0.00546 |
| Opus 5.5 | $0.00014 | $0.00218 |
| Sonnet 5.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 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.
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.
- 1mo 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 (12 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 546 once invoked, about $0.0001 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…