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/cacr92/wereply/debuggingnpx skills add cacr92/WeReply --skill debugginggit clone --depth 1 https://github.com/cacr92/WeReplyWhat 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.00159 | $0.03840 |
| Opus 5 | $0.00079 | $0.01920 |
| Sonnet 5 | $0.00032 | $0.00768 |
| Haiku 4.5 | $0.00016 | $0.00384 |
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 — 660 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging Skill
Systematic debugging strategies for diagnosing and fixing issues in Tauri applications.
Overview
This skill provides debugging guidance for:
- Rust backend issues: Panics, errors, async problems, database failures
- React frontend issues: Runtime errors, UI problems, state management issues
- Integration problems: Tauri command failures, type mismatches, serialization errors
- Database issues: Query failures, connection problems, migration errors
- Performance issues: Slow operations, memory leaks, blocking calls
When This Skill Applies
This skill activates when:
- Application crashes or panics
- Functions return errors
- UI doesn't work as expected
- Tests are failing
- Performance is degraded
- Data is incorrect or corrupted
- Features don't work together properly
Debugging Framework
The Scientific Method
- Observe: What exactly is happening?
- Formulate Hypothesis: What could be causing this?
- Test Hypothesis: How can we verify?
- Analyze Results: Does this confirm or reject hypothesis?
- Iterate: If not solved, form new hypothesis
Systematic Debugging Process
┌─────────────────┐
│ 1. Define Issue │
│ What is the │
│ symptom? │
└────────┬────────┘
│
▼
┌─────────────────┐
│ 2. Gather Info │
│ Error msg? │
│ Stack trace? │
│ Logs? │
└────────┬────────┘
│
▼
┌─────────────────┐
│ 3. Reproduce │
│ Can we make │
│ it happen │
│ consistently?│
└────────┬────────┘
│
▼
┌─────────────────┐
│ 4. Isolate │
│ Narrow down │
│ location │
└────────┬────────┘
│
▼
┌─────────────────┐
│ 5. Fix & Test │
│ Apply fix │
│ Verify it │
│ works │
└─────────────────┘
Common Issues & Solutions
Rust Backend Issues
Issue: "Function not found" for Tauri Command
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 660 lines · 159 tokens per session scan A 279245250b54
debugging is a skill published in the GitHub repository cacr92/WeReply (6 stars, last pushed 7mo ago), licensed MIT. It adds 159 tokens to every session and 3,840 once invoked, about $0.0008 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 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…