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/apexiq/skillsmith/debuggingnpx skills add ApexIQ/skillsmith --skill debugginggit clone --depth 1 https://github.com/ApexIQ/skillsmithWhat 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.00025 | $0.00518 |
| Opus 5 | $0.00013 | $0.00259 |
| Sonnet 5 | $0.00005 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
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
Philosophy: A bug is a gift. It reveals a gap in your tests or understanding.
Workflow
1. Reproduce
- First, reproduce the bug reliably. If you can't reproduce it, you can't fix it.
- Get exact steps, input, and environment.
- Create a minimal test case that fails.
2. Isolate
- Narrow down the scope: Frontend or Backend? Which function?
- Use logging or debugger to inspect state at key points.
- Binary Search: Comment out half the code. Does bug persist? Narrow down.
3. Diagnose
- Ask: "What did I expect? What actually happened?"
- Check recent changes (
git log,git blame). - Inspect data entering and leaving suspect functions.
4. Fix & Verify
- Write a test that fails due to the bug. (TDD for bugs!)
- Implement the fix.
- Run the test. It MUST pass.
- Run full test suite to check for regressions.
5. Document
- Add a comment explaining why the bug occurred.
- If subtle, add to "Known Gotchas" in documentation.
Common Bug Patterns
| Symptom | Likely Cause |
|---|---|
| Works locally, fails in CI | Environment differences, missing env vars |
| Works sometimes | Race condition, timing issue |
| Returns null/undefined | Missing null check, async timing |
| Wrong data displayed | API mismatch, caching issue |
Examples
1. Bug: "Submit button does nothing."
2. Isolate: Is onClick firing? -> Add console.log.
3. Diagnose: Handler fires, but API returns 500.
4. Root Cause: Endpoint expects different payload format.
5. Fix: Update request payload. Add test.
Guidelines
- Never guess. Always verify with logs or debugger.
- Don't just patch symptoms. Find the root cause.
- If bug took >30 mins to find, add a test to prevent recurrence.
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 · 65 lines · 25 tokens per session scan A cd4311eab203
debugging is a skill published in the GitHub repository ApexIQ/skillsmith (5 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 518 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 skills, from other repositories
rove
Use when controlling Rove tasks, parallel coding attempts, hosted agent sessions, task lifecycle, or the daemon-owned issue tracker from a shell. Also the ONLY channel for messaging another agent session on this machine — rove api send, never a peer/MCP side channel.
release
Autonomously cut a Rove (@sma1lboy/rove) release end-to-end — detect the semver bump from pending changesets (flagging an upstream minor you didn't intend), run the release gates, bump/tag/push via scripts/release.sh, then poll the GitHub Actions Release workflow with gh until npm publish completes, diagnosing CI…
hyperframes-cli
HyperFrames CLI dev loop. Use when running npx hyperframes init, add, catalog, capture, lint, validate, inspect, layout, snapshot, preview, play, render, publish, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, or remove-background, or when troubleshooting the…
changelog-generator
Draft Rove release notes as Changesets. Writes user-facing entries as .changeset/.md files for @sma1lboy/rove (consumed into packages/kobe/CHANGELOG.md at release time). Use when the user asks for "changelog", "release notes", "what changed", "add a changeset", or before cutting a version. Enforces Rove's no-soft-wrap…
token-saver-config
Configure and diagnose token-saver compression settings. Use when the user asks about adjusting compression levels, checking processor status, debugging hook issues, or reviewing savings statistics.
pstack
Rigorous engineering mode for nontrivial work in this repo — a set of named principles plus the leaf skills that apply them. Use when the user says "pstack", "go deep", "be rigorous", "认真做", or when a task involves architecture, a real bug, a refactor, or anything the user will not be watching. Ported from…