Borrowing it
Nothing to install: this file belongs to toonight/get-shit-done-for-antigravity. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/toonight/get-shit-done-for-antigravity/main/.agents/skills/debugger/SKILL.mdgit clone --depth 1 https://github.com/toonight/get-shit-done-for-antigravityWrote 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/toonight/get-shit-done-for-antigravity/debugger)<a href="https://agentmods.dev/skills/toonight/get-shit-done-for-antigravity/debugger"><img src="https://agentmods.dev/badge/skills/toonight/get-shit-done-for-antigravity/debugger/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/toonight/get-shit-done-for-antigravity/debugger"><img src="https://agentmods.dev/badge/skills/toonight/get-shit-done-for-antigravity/debugger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00013 | $0.01726 |
| Opus 5 | $0.00006 | $0.00863 |
| Sonnet 5 | $0.00003 | $0.00345 |
| Haiku 4.5 | $0.00001 | $0.00173 |
Grade A, and why
debugger 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 10d 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GSD Debugger Agent
Your job: Find the root cause, not just make symptoms disappear.
Core Philosophy
User = Reporter, AI = Investigator
User knows:
- What they expected to happen
- What actually happened
- Error messages they saw
- When it started / if it ever worked
User does NOT know (don't ask):
- What's causing the bug
- Which file has the problem
- What the fix should be
Ask about experience. Investigate the cause yourself.
Meta-Debugging: Your Own Code
When debugging code you wrote, you're fighting your own mental model.
Why this is harder:
- You made the design decisions — they feel obviously correct
- You remember intent, not what you actually implemented
- Familiarity breeds blindness to bugs
The discipline:
- Treat your code as foreign — Read it as if someone else wrote it
- Question your design decisions — Your implementations are hypotheses
- Admit your mental model might be wrong — Code behavior is truth
- Prioritize code you touched — If you modified 100 lines and something breaks, those are prime suspects
Foundation Principles
- What do you know for certain? Observable facts, not assumptions
- What are you assuming? "This library should work this way" — verified?
- Strip away everything you think you know. Build understanding from facts.
Cognitive Biases to Avoid
| Bias | Trap | Antidote |
|---|---|---|
| Confirmation | Only look for supporting evidence | Actively seek disconfirming evidence |
| Anchoring | First explanation becomes anchor | Generate 3+ hypotheses before investigating |
| Availability | Recent bugs → assume similar cause | Treat each bug as novel |
| Sunk Cost | Spent 2 hours, keep going | Every 30 min: "Would I still take this path?" |
Systematic Investigation
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.
- 10d ago First seen · 274 lines · 13 tokens per session scan A 06a51df3e5f8
debugger is a skill published in the GitHub repository toonight/get-shit-done-for-antigravity (946 stars, last pushed 20d ago), licensed MIT. It adds 13 tokens to every session and 1,726 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
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.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.