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/fixnpx skills add arbazkhan971/godmode --skill fixgit clone --depth 1 https://github.com/arbazkhan971/godmodeWrote 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/arbazkhan971/godmode/fix)<a href="https://agentmods.dev/skills/arbazkhan971/godmode/fix"><img src="https://agentmods.dev/badge/skills/arbazkhan971/godmode/fix.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.00057 | $0.01194 |
| Opus 5 | $0.00028 | $0.00597 |
| Sonnet 5 | $0.00011 | $0.00239 |
| Haiku 4.5 | $0.00006 | $0.00119 |
Grade A, and why
fix 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 5d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Activate When
/godmode:fix, "fix this", "tests failing"- Build, lint, or test returns non-zero exit code
- Called by other skills when checks fail
Fix vs Debug Handoff
/godmode:fix assumes root cause is KNOWN.
If root cause unknown: route to /godmode:debug.
Workflow
# Detect stack and run checks
build_cmd 2>&1; echo "EXIT: $?"
lint_cmd 2>&1; echo "EXIT: $?"
test_cmd 2>&1; echo "EXIT: $?"
LOOP:
error_count = run_all_checks()
original = error_count
IF error_count == 0: STOP — all checks pass
WHILE error_count > 0:
1. TRIAGE — priority: build > type > lint > test
Run failing check, parse errors
2. PICK — highest priority, not in skipped_list
Create signature: "{file}:{line}:{error_code}"
3. ANALYZE — read FULL error output (all lines)
Read source at file:line +/- 15 lines
Name mismatch: "expected X, got Y because Z"
4. FIX — change <= 5 lines for ONE error
Fix cause, not symptom
5. COMMIT — git add + commit before verify
6. VERIFY — new_count = run_all_checks()
IF new_count >= error_count:
git reset --hard HEAD~1
attempt_count[signature] += 1
IF attempt_count >= 3: skip error
ELSE: error_count = new_count
7. LOG — append to .godmode/fix-results.tsv
THRESHOLDS:
Max attempts per error: 3
Max lines changed per fix: 5
Status report: every 5 iterations
Consecutive reverts to stop: 5
IF all errors skipped: recommend /godmode:debug
One Fix Per Iteration
Fix ONE error per iteration. Verify. Commit. Next. Never batch-fix multiple errors in one commit. Each fix independently verifiable and revertable.
Output Format
Triage: {build|lint|test} failing with {N} errors
Pick: Fixing [{iter}/{original}]: {type} at {file}:{line}
Analyze: Root cause: {expected} vs {actual}
Verify (kept): KEPT: count {before} → {after}
Verify (revert): REVERTED: attempt {N}/3
Status: {remaining} remaining (from {original})
Final: Fixed: {original} → {count} in {N} iters.
Skipped: {list}.
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.
- 5d ago First seen · 144 lines · 57 tokens per session scan A 2913143634bc
fix is a skill published in the GitHub repository arbazkhan971/godmode (26 stars, last pushed 7d ago), licensed MIT. It adds 57 tokens to every session and 1,194 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-30.
Other skills, from other repositories
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.
agent-code-generator
Generates Agent definitions (.md files) based on user intent and standard templates.
codex
Run benchmark-selected GPT-5.6 work through the Codex CLI.
scienceworld-growth-focuser
Use when you have planted a seed or need to track a plant's growth stage (sprouting, flowering, reproduction). Applies the 'focus on' action to a specific plant or biological entity to signal intent and monitor its development. Trigger after planting or when you need to observe life cycle progression in the…
iterate-pivot-decision
Documents a strategic pivot or persevere decision with the evidence, analysis, and rationale. Use when evaluating whether to change direction on a product, feature, or strategy based on market feedback.