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/youglin-dev/aha-loop/god-interventionnpx skills add YougLin-dev/Aha-Loop --skill god-interventiongit clone --depth 1 https://github.com/YougLin-dev/Aha-LoopWhat 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.00037 | $0.02365 |
| Opus 5 | $0.00018 | $0.01182 |
| Sonnet 5 | $0.00007 | $0.00473 |
| Haiku 4.5 | $0.00004 | $0.00236 |
Grade A, and why
god-intervention 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.
How it starts
The opening of the file, as written. The whole thing — 463 lines — stays where its author put it; the contents beside it link to each section on GitHub.
God Committee Intervention Skill
Purpose
This skill guides God Committee members through executing interventions - from minor repairs to major system modifications.
Intervention Severity Levels
Level 1: Minor Repair
- Fix corrupted files
- Clear stale locks
- Truncate large logs
- Fix permissions
Consensus Required: No
Level 2: Process Control
- Pause execution
- Resume execution
- Terminate specific processes
Consensus Required: No (unless terminating all)
Level 3: Code Modification
- Fix bugs directly
- Update configurations
- Modify skills
- Add documentation
Consensus Required: Recommended
Level 4: Major Rollback
- Revert multiple commits
- Undo PRD progress
- Reset system state
Consensus Required: Yes
Level 5: System Termination
- Stop all execution
- Archive project state
- Full system shutdown
Consensus Required: Yes
Pre-Intervention Checklist
Before any intervention:
## Pre-Intervention Checklist
- [ ] Issue clearly identified and documented
- [ ] Evidence gathered (logs, metrics, observations)
- [ ] Impact assessment completed
- [ ] Rollback plan prepared
- [ ] Consensus obtained (if required)
- [ ] Execution layer paused (if needed)
- [ ] Backup created (if applicable)
Executing Interventions
Level 1: Minor Repairs
# Clear stale locks
./scripts/god/powers.sh repair lock
# Clean up worktrees
./scripts/god/powers.sh repair worktrees
# Fix corrupted JSON files
./scripts/god/powers.sh repair json
# Truncate large logs
./scripts/god/powers.sh repair logs
# Fix script permissions
./scripts/god/powers.sh repair permissions
# Clean git state
./scripts/god/powers.sh repair git
# Run all repairs
./scripts/god/powers.sh repair all
Level 2: Process Control
Pausing Execution
# Pause with reason
./scripts/god/powers.sh pause "Investigation needed: failing tests" YOUR_ID
# Check pause status
./scripts/god/powers.sh pause-status
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 · 463 lines · 37 tokens per session scan A f2b74c9d580f
god-intervention is a skill published in the GitHub repository YougLin-dev/Aha-Loop (181 stars, last pushed 7mo ago), licensed MIT. It adds 37 tokens to every session and 2,365 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…