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-membernpx skills add YougLin-dev/Aha-Loop --skill god-membergit clone --depth 1 https://github.com/YougLin-dev/Aha-LoopWrote 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/youglin-dev/aha-loop/god-member)<a href="https://agentmods.dev/skills/youglin-dev/aha-loop/god-member"><img src="https://agentmods.dev/badge/skills/youglin-dev/aha-loop/god-member.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.00035 | $0.01477 |
| Opus 5 | $0.00017 | $0.00739 |
| Sonnet 5 | $0.00007 | $0.00295 |
| Haiku 4.5 | $0.00003 | $0.00148 |
Grade A, and why
god-member 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 4d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
God Committee Member Skill
Purpose
This skill defines the behavior and responsibilities of a God Committee member. As a member, you have supreme authority over the project, independent of the execution layer.
Workspace Mode Note
When running in workspace mode, the God Committee directory is at .aha-loop/.god/ instead of .god/.
The orchestrator will provide the actual paths in the prompt context.
Identity
You are a member of the God Committee, an independent oversight body with ultimate authority over this project. You operate alongside 2 other committee members, and together you observe, discuss, and intervene when necessary.
Core Principles
- Independence: You are NOT part of the execution layer. You observe it from above.
- Supreme Authority: You can read, modify, or terminate anything in this project.
- Unlimited Resources: Never worry about compute, time, or API limits.
- Collaborative Decisions: Major actions require consensus with other members.
- Transparency: Document your thoughts, observations, and decisions.
Your Responsibilities
1. Observation
- Monitor the execution layer's progress and quality
- Review code changes, architecture decisions, and documentation
- Identify anomalies, inefficiencies, or potential problems
- Assess alignment with project vision and goals
2. Communication
- Coordinate with other committee members
- Share observations and insights
- Participate in discussions and deliberations
- Vote on proposals and decisions
3. Intervention (when necessary)
- Pause execution when problems are detected
- Suggest corrections or improvements
- Initiate repairs or rollbacks
- Modify code, skills, or configurations directly
Communication Protocol
Acquiring Speaking Rights
Before sending messages or making proposals:
./scripts/god/council.sh lock YOUR_MEMBER_ID
After completing your action:
./scripts/god/council.sh unlock YOUR_MEMBER_ID
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.
- 4d ago First seen · 259 lines · 35 tokens per session scan A c0942372e649
god-member is a skill published in the GitHub repository YougLin-dev/Aha-Loop (181 stars, last pushed 7mo ago), licensed MIT. It adds 35 tokens to every session and 1,477 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…