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-consensusnpx skills add YougLin-dev/Aha-Loop --skill god-consensusgit 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.00039 | $0.01959 |
| Opus 5 | $0.00019 | $0.00979 |
| Sonnet 5 | $0.00008 | $0.00392 |
| Haiku 4.5 | $0.00004 | $0.00196 |
Grade A, and why
god-consensus 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
God Committee Consensus Skill
Purpose
This skill guides God Committee members through the consensus-building process for making collective decisions.
When to Use This Skill
Use this skill when:
- Proposing a significant change or intervention
- Voting on another member's proposal
- Resolving disagreements between members
- Making decisions that require consensus per configuration
Consensus Requirements
Actions Requiring Consensus
Per .god/config.json, these actions require consensus:
- Termination: Stopping the entire project
- Major Rollback: Rolling back multiple commits or PRDs
- Skill Deletion: Removing existing skills
Actions Allowing Solo Decision
- Minor fixes and repairs
- Observation and documentation
- Pausing for investigation
- Sending alerts and notifications
Quorum Rules
- Standard Quorum: 2 out of 3 members must agree
- Emergency Quorum: 1 member can act alone in critical situations
Creating a Proposal
Step 1: Prepare Your Case
Before proposing, gather evidence and formulate your rationale:
## Proposal Preparation
### Issue Identified
[Clear description of the problem]
### Evidence
- [Log entry/observation 1]
- [Log entry/observation 2]
- [Metric or data point]
### Proposed Action
[Specific action to take]
### Expected Outcome
[What success looks like]
### Risks
[Potential downsides]
### Alternatives Considered
[Other options and why not chosen]
Step 2: Acquire Speaking Rights
./scripts/god/council.sh lock YOUR_ID
Step 3: Create the Proposal
./scripts/god/council.sh propose YOUR_ID "TYPE" "DESCRIPTION" "RATIONALE"
Proposal Types:
intervention- Active intervention in executionrepair- Fix or repair actionpolicy_change- Change to rules or configurationtermination- Stop project executionrollback- Revert to previous state
Example:
./scripts/god/council.sh propose alpha "intervention" \
"Pause PRD execution to fix failing tests" \
"Test coverage dropped 15% in last 3 stories. Need to address before proceeding."
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 · 360 lines · 39 tokens per session scan A 101b846e0bdd
god-consensus is a skill published in the GitHub repository YougLin-dev/Aha-Loop (181 stars, last pushed 7mo ago), licensed MIT. It adds 39 tokens to every session and 1,959 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…