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 girijashankarj/cursor-handbook --skill debug-issuegit clone --depth 1 https://github.com/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/debug-issue)<a href="https://agentmods.dev/skills/girijashankarj/cursor-handbook/debug-issue"><img src="https://agentmods.dev/badge/skills/girijashankarj/cursor-handbook/debug-issue.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.1 | $0.00034 | $0.00220 |
| Opus 5 | $0.00017 | $0.00110 |
| Sonnet 5 | $0.00007 | $0.00044 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
debug-issue 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 3d 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
Skill: Debug issue
Trigger
When the user asks to debug a bug, find the root cause, or fix a failing scenario.
Steps
- Reproduce — Run or describe steps to reproduce; capture error message and stack if any.
- Isolate — Narrow to the smallest repro (single request, single file, single branch).
- Hypothesize — List 2–3 likely causes (e.g. null input, wrong config, race).
- Verify — Add a log, assertion, or minimal test to confirm one cause.
- Fix — Apply minimal code change; add or update a test to prevent regression.
- Confirm — Run type-check and relevant tests.
Rules
- Do not change unrelated code.
- Prefer adding a test that fails before the fix and passes after.
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.
- 3d ago First seen · 23 lines · 34 tokens per session scan A 60ddea92eeae
debug-issue is a skill published in the GitHub repository girijashankarj/cursor-handbook (30 stars, last pushed 7d ago), licensed MIT. It adds 34 tokens to every session and 220 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
mockito
Use when generating mocks, stubbing methods, verifying interactions, capturing arguments, or choosing between mocks, fakes, and real objects (Mockito).
mocktail
Use when creating mocks, stubbing methods, verifying interactions, registering fallback values, or choosing between mocks, fakes, and real objects (Mocktail).
iterate-agent-harness
Turn an agent failure—premature stop, false completion, gamed check, missed file, broken handoff—into a durable rule/skill/hook/CI guard plus regression test. Use when "the agent stopped early again", "it gamed the test", or "add a guard so this doesn't recur". App bugs → workflow-fix-and-ship.
mushi-integration
Full end-to-end Mushi Mushi integration smoke test: bug capture → AI triage → story mapping → TDD test generation → approval → execution → PDCA cycle. Use when "test mushi integration", "verify full pipeline", "mushi e2e check", "does mushi work end-to-end", "smoke test mushi", or after deploying changes.
unit-core-logic-testing
Validate pure functions, deterministic logic, and core algorithms in OBS and PIPE. Use when testing DAG evaluation, GitOps parsing, error propagation, or ensuring deterministic outputs.