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 skills add KingEmma7/cursor-os --skill debugging-loopgit clone --depth 1 https://github.com/KingEmma7/cursor-osWrote 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/kingemma7/cursor-os/debugging-loop)<a href="https://agentmods.dev/skills/kingemma7/cursor-os/debugging-loop"><img src="https://agentmods.dev/badge/skills/kingemma7/cursor-os/debugging-loop/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/kingemma7/cursor-os/debugging-loop"><img src="https://agentmods.dev/badge/skills/kingemma7/cursor-os/debugging-loop.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00037 | $0.00332 |
| Opus 5.5 | $0.00015 | $0.00133 |
| Sonnet 5.5 | $0.00007 | $0.00066 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
debugging-loop 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 1mo 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 Loop
Find the root cause before changing code. Resist the urge to guess-and-patch.
1. Reproduce
- Establish exact, reliable repro steps. Capture the full error, stack trace, and the expected-vs-actual behavior.
- If you can't reproduce it, gather more evidence (logs, inputs, environment) before proceeding.
2. Isolate
- Read the failing code path and form a specific hypothesis about the cause.
- Narrow the surface: bisect inputs, add targeted logging or a failing test, or check recent changes. Confirm the hypothesis with evidence before editing.
- Distinguish the symptom from the cause. The first error in the chain is often not the real one.
3. Fix
- Change the root cause, not the symptom. Don't mask it with broad try/catch, retries, or silenced output.
- Make the smallest fix that resolves it. Keep unrelated cleanup out of the bugfix.
4. Verify
- Add or run a check that fails before the fix and passes after — a regression test where practical.
- Run the surrounding tests and confirm the fix didn't break adjacent behavior.
5. Capture
- Report the root cause, the evidence, the fix, and how you verified it.
- If this bug points to a recurring trap, record it in
docs/repo-memory.mdso it doesn't bite again.
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.
- 1mo ago First seen · 35 lines · 37 tokens per session scan A f62652e47068
debugging-loop is a skill published in the GitHub repository KingEmma7/cursor-os (2 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 332 once invoked, about $0.0001 per session on Opus 5.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
trellis-survey
Check this template's static wiring and setup - missing hooks, unreachable skills, unfinished context files. Runtime activation and trust require separate checks. Read-only. Use when asked "what do I have", "is everything set up", "what is actually running", "audit my setup", "did I break anything", "what did I…
bug-report
Structured bug-fix protocol per docs/methodology/bug-protocol.md. Use when asked to '/bug-report', 'I found a bug', 'something is broken', 'fix this bug', 'report a bug', 'this is broken'.
debugging-strategies
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
sql-optimization-patterns
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.
parallel-debugging
Debug complex issues using competing hypotheses with parallel investigation, evidence collection, and root cause arbitration. Use this skill when debugging bugs with multiple potential causes, performing root cause analysis, or organizing parallel investigation workflows.