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/arvoreeducacao/rhm/debuggingnpx skills add arvoreeducacao/rhm --skill debugginggit clone --depth 1 https://github.com/arvoreeducacao/rhmWhat 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.00027 | $0.00358 |
| Opus 5 | $0.00014 | $0.00179 |
| Sonnet 5 | $0.00005 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
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.
What it actually says
Debugging
Use this skill for systematic diagnosis of complex problems, root cause analysis, and resolution.
Context collection
Before starting, collect:
| Information | Why it matters |
|---|---|
| Symptoms and error messages | Starting point for investigation |
| Environment (dev/staging/prod) | Determines available tools and access |
| Steps to reproduce | Allows hypothesis validation |
| Timeline of when it started | Correlates with deploys/changes |
| Recent changes | Primary candidates for root cause |
Diagnostic approach
- Symptom analysis — Understand exactly what's happening
- Hypothesis formation — List possible causes ordered by probability
- Systematic elimination — Test each hypothesis methodically
- Evidence collection — Document logs, stack traces, data
- Root cause isolation — Find the real cause, not just symptoms
- Solution validation — Confirm the fix resolves the problem
Tools
- database MCPs to check suspicious data states
- monitoring MCPs (Datadog, SigNoz, etc.) for metrics and logs
- infrastructure MCPs (AWS, Kubernetes) for production debugging
- the relevant tech skill to understand expected patterns
Resolution checklist
- Issue reproduced consistently
- Hypotheses documented and tested
- Root cause identified with evidence
- Fix implemented
- Side effects verified
- Test added to prevent regression (if applicable)
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 · 47 lines · 27 tokens per session scan A 4f8928a37c2e
debugging is a skill published in the GitHub repository arvoreeducacao/rhm (19 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 358 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-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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.