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/airvalona/antigravity-like-claude-code/debugnpx skills add airvalona/antigravity-like-claude-code --skill debuggit clone --depth 1 https://github.com/airvalona/antigravity-like-claude-codeWrote 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/airvalona/antigravity-like-claude-code/debug)<a href="https://agentmods.dev/skills/airvalona/antigravity-like-claude-code/debug"><img src="https://agentmods.dev/badge/skills/airvalona/antigravity-like-claude-code/debug.svg" alt="Measured on agentmods" 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 | $0.00064 | $0.00444 |
| Opus 5 | $0.00032 | $0.00222 |
| Sonnet 5 | $0.00013 | $0.00089 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
debug 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 4d 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
/debug — Structured Debugging Workflow
Port of Claude Code's /debug.
Arguments
/debug <description or error>— start debugging that specific issue
Steps
-
Reproduce first. Before theorizing, try to actually trigger the bug (run the failing command/test, hit the failing code path). If it can't be reproduced with what's available, say so and ask for the missing piece (repro steps, input data, environment detail) rather than guessing.
-
Isolate. Narrow down from "something is wrong" to the specific function/line/condition:
- Read the stack trace bottom-up if one exists
- Add temporary logging/print statements at the narrowing points if needed, and remove them once the cause is found
- Check recent changes to the affected area first (
git log -p <file>/git blame) since regressions are more likely near recent edits
-
Form a hypothesis for the root cause before writing any fix. State it explicitly: "This happens because X does Y when Z."
-
Verify the hypothesis — confirm it actually explains the observed behavior (e.g. by triggering the exact condition and seeing the exact failure) before proposing a fix. Don't patch symptoms without confirming the cause.
-
Propose and apply the fix, then re-run the original repro to confirm it's actually resolved — not just that the code compiles/runs.
-
Clean up any temporary debug logging added during the process unless the user wants it kept.
Notes
Resist the urge to fix multiple unrelated things noticed along the way — note them for the user instead of scope-creeping the debug session.
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.
- 4d ago First seen · 45 lines · 64 tokens per session scan A 9af8916ab0a8
debug is a skill published in the GitHub repository airvalona/antigravity-like-claude-code (2 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 444 once invoked, about $0.0003 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…