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/arbazkhan971/godmode/debugnpx skills add arbazkhan971/godmode --skill debuggit clone --depth 1 https://github.com/arbazkhan971/godmodeWhat 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.00018 | $0.01831 |
| Opus 5 | $0.00009 | $0.00915 |
| Sonnet 5 | $0.00004 | $0.00366 |
| Haiku 4.5 | $0.00002 | $0.00183 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Activate When
/godmode:debug, "why is this happening?", "this doesn't work"
Lessons Integration
Before investigation: read .godmode/lessons.md for known root causes and debugging shortcuts.
After session: append lessons about root cause patterns discovered.
The Loop
failing_count = run_tests() # test_cmd (from stack detection), count failures
current_iteration = 0
skipped = 0
WHILE failing_count > 0 AND skipped < 3:
current_iteration += 1
bug = pick_highest_severity(remaining_bugs)
technique_index = 0
techniques = [stack_trace, git_bisect, state_inspection, binary_search]
# 1. REPRODUCE — run failing command 3x. Consistent failure = real bug. Intermittent = add to flaky list.
# 2. SELECT TECHNIQUE (max 5 min each):
Stack trace → Trace Analysis | "Used to work" → `git bisect` | Regression → `git log -20`
Intermittent/Wrong results → State Inspection | Unknown → Binary Search (eliminate half)
# 3. INVESTIGATE — insert print/log at suspect file:line. Log: variable name=value, caller, actual vs expected.
# 4. PROVE — state: "Bug is at {file}:{line} because {variable}={actual}, expected {expected}. Reproduce: {cmd}."
Chain: Symptom → Why? → Why? → Root cause → Fix (file:line + diff). Min 3 'why's.
# Root cause found → KEEP (fix or hand off)
# Root cause NOT found → try next technique (step 2)
# All techniques exhausted → DISCARD bug (skip++), log reason_stuck + root_cause_unknown
# 5. FIX OR HAND OFF — see Fix Handoff Protocol below
# 6. VERIFY — re-run failing test. Then run full suite to check for regressions.
# 7. APPEND .godmode/debug-findings.tsv: iteration, bug_id, symptom, root_cause, file:line, fix_commit, status(fixed/skipped), reason_stuck
# 8. STATUS every 3: "{found} found, {failing_count} remaining, {skipped} skipped"
failing_count = run_tests()
IF skipped >= 3: STOP, report partial results
Stuck Criteria
IF stuck >3 iterations on same bug:
→ Discard bug, move to next
→ Log: bug_id, reason_stuck, root_cause_unknown, skipped=true
→ Max skipped bugs: 3. After 3 skipped → stop, report partial
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 163 lines · 18 tokens per session scan A 7e0038619348
debug is a skill published in the GitHub repository arbazkhan971/godmode (26 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 1,831 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
happiness-skill
当用户问「怎么才能更幸福/为什么得到了还不满足/怎么减少焦虑」时调用。 核心理念: 幸福是缺憾感清空的默认状态, 是可训练的技能; 欲望是与自己的契约(得到前不快乐), 同时只留一个重大欲望; 活在当下。 不适用于: 临床抑郁等需要专业治疗的场景(本书方法不能替代医疗)。 Triggers: 幸福/不快乐/欲望/焦虑/知足/活在当下/happiness/desire/anxiety.
influence-psychology
Apply the seven principles of ethical persuasion (reciprocity, commitment, social proof, authority, liking, scarcity, unity) to product design, copy, and sales. Use when the user mentions "social proof", "persuasive copy", "why users dont convert", "ethical persuasion", "reciprocity", "scarcity tactics", "commitment…
jobs-to-be-done
Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also…
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
pcbway
PCBWay PCB fabrication and assembly — turnkey/consigned assembly, design rules, ordering workflow. Alternative to JLCPCB for manufacturing. Use with KiCad. Use this skill when the user mentions PCBWay, needs turnkey assembly (PCBWay sources parts by MPN), has parts not available on LCSC, needs assembled boards with…
grid-ctf-ops
Operational knowledge for the gridctf scenario including strategy playbook, lessons learned, and resource references. Use when generating, evaluating, coaching, or debugging gridctf strategies.