New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

God Consensus

by YougLin-dev in YougLin-dev/Aha-Loop

Guides God Committee members through consensus-building for collective decisions.

MITAuto-check passedSales & Support

Install God Consensus

skills CLI
$ npx skills add YougLin-dev/Aha-Loop --skill god-consensus -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install YougLin-dev/Aha-Loop god-consensus --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/YougLin-dev/Aha-Loop.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/god-consensus .claude/skills/god-consensus && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
god-consensus
GitHub stars
181
Token cost
~2k tokens
SKILL.md length
549 words
Files
1
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

Guides God Committee members through consensus-building for collective decisions.

  • Works in 9 steps: Prepare Your Case → Acquire Speaking Rights → Create the Proposal → …
  • Disagreement resolution
  • SKILL.md covers Purpose, When to Use This Skill, Consensus Requirements and Creating a Proposal, plus 4 more sections
  • Calls jq

What it does

God Consensus is an agent skill from YougLin-dev/Aha-Loop. Guides God Committee members through consensus-building for collective decisions. Use for proposals, voting, and disagreement resolution. Triggers on: consensus, voting, proposal, committee decision.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support, covering Proposals and quotes. The repository describes itself as: [MVP] Aha Loop is a fully autonomous AI development system, extended from the core ideas of Ralph. It's not just an execution engine, but a complete AI development framework with… The licence is MIT.

When your agent uses it

  • Disagreement resolution
  • Committee decision

Example prompts

  • “Use the god-consensus skill to guide God Committee members through consensus-building for collective decisions”
  • “/god-consensus”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Prepare Your Case
  2. Acquire Speaking Rights
  3. Create the Proposal
  4. Notify Members
  5. Release Speaking Rights
  6. Review the Proposal
  7. Analyze the Proposal
  8. Cast Your Vote
  9. Document Your Reasoning

What it can do on your machine

Read from SKILL.md and the folder at commit 8d799b2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

God Consensus loads about 2k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 549 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~53
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from YougLin-dev/Aha-Loop at commit 8d799b2, republished under its MIT licence (© YougLin-dev). 549 words, ~1,961 tokens.

Download SKILL.mdSave it as .claude/skills/god-consensus/SKILL.md (or your agent's skills folder).
name
god-consensus
description
Guides God Committee members through consensus-building for collective decisions. Use for proposals, voting, and disagreement resolution. Triggers on: consensus, voting, proposal, committee decision.

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:

markdown
## 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
bash
./scripts/god/council.sh lock YOUR_ID
Step 3: Create the Proposal
bash
./scripts/god/council.sh propose YOUR_ID "TYPE" "DESCRIPTION" "RATIONALE"

Proposal Types:

  • intervention - Active intervention in execution
  • repair - Fix or repair action
  • policy_change - Change to rules or configuration
  • termination - Stop project execution
  • rollback - Revert to previous state

Example:

bash
./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."
Step 4: Notify Members

The proposal system automatically notifies all members. The message will be in their inboxes.

Step 5: Release Speaking Rights
bash
./scripts/god/council.sh unlock YOUR_ID

Voting on Proposals

Step 1: Review the Proposal
bash
# Check pending decisions
./scripts/god/council.sh status

# Read the specific proposal
cat .god/council/decisions/DECISION_ID.json | jq '.'
Step 2: Analyze the Proposal

Consider these questions:

  1. Is the problem real?

    • Verify the evidence
    • Check if it's already being addressed

  2. Is the solution appropriate?

    • Will it solve the problem?
    • Are there better alternatives?
    • What are the side effects?

  3. Is it timely?

    • Is immediate action needed?
    • Can we wait for more information?
Step 3: Cast Your Vote
bash
./scripts/god/council.sh lock YOUR_ID
./scripts/god/council.sh vote YOUR_ID "DECISION_ID" "VOTE" "COMMENT"
./scripts/god/council.sh unlock YOUR_ID

Vote Options:

  • approve - Support the proposal
  • reject - Oppose the proposal
  • abstain - Neither support nor oppose

Example:

bash
./scripts/god/council.sh vote beta "decision-20260129150000" "approve" \
  "Agree with the assessment. Tests should be fixed before proceeding."
Step 4: Document Your Reasoning

Always add a comment explaining your vote:

markdown
## Vote: [APPROVE/REJECT/ABSTAIN]

### Reasoning
[Why you voted this way]

### Conditions (if any)
[Conditions for your support]

### Alternative Suggestion (if rejecting)
[What you'd propose instead]

Reaching Consensus

Unanimous Agreement

Ideal scenario - all members agree:

Alpha: approve
Beta: approve  
Gamma: approve
Result: APPROVED (unanimous)
Majority Agreement

Quorum reached with majority:

Alpha: approve
Beta: approve
Gamma: reject
Result: APPROVED (2/3 majority)
Split Decision

When members disagree significantly:

  1. Initiate Discussion Session

    bash
    ./scripts/god/council.sh session-start "Resolving: PROPOSAL_TOPIC"

  2. Each Member States Position

    • Present full reasoning
    • Listen to others' concerns
    • Look for common ground

  3. Seek Compromise

    • Modify the proposal
    • Add conditions
    • Split into smaller decisions

  4. Re-vote if Needed

    • Create amended proposal
    • Vote again
Show full SKILL.md (200 more words)Show less
Deadlock Resolution

If consensus cannot be reached:

  1. Defer Decision

    • Wait for more information
    • Set review deadline

  2. Escalate Scope

    • Break into smaller decisions
    • Address sub-issues separately

  3. Time-box Discussion

    • Set deadline for decision
    • Default action if no consensus

Emergency Consensus

In critical situations, expedited consensus is allowed:

Emergency Criteria
  • System crash or imminent failure
  • Security breach
  • Data loss risk
  • Infinite loop/resource exhaustion
Emergency Protocol

  1. Declare Emergency

    bash
    ./scripts/god/awakener.sh critical "REASON"

  2. Take Immediate Action

    • One member can act alone
    • Document the action immediately

  3. Post-Action Review

    • Inform other members ASAP
    • Document full rationale
    • Get retroactive approval
Emergency Action Template
markdown
## Emergency Action Report

### Timestamp
[When action was taken]

### Acting Member
[Who took the action]

### Situation
[What triggered the emergency]

### Action Taken
[What was done]

### Justification
[Why immediate action was needed]

### Outcome
[Result of the action]

### Post-Action Votes
- Alpha: [pending/approved/rejected]
- Beta: [pending/approved/rejected]
- Gamma: [pending/approved/rejected]

Consensus Best Practices

Do
  • ✅ Present clear evidence
  • ✅ Consider all perspectives
  • ✅ Propose specific, actionable items
  • ✅ Accept compromise when reasonable
  • ✅ Document all reasoning
  • ✅ Respect deadlines
Don't
  • ❌ Vote without reviewing the proposal
  • ❌ Reject without suggesting alternatives
  • ❌ Take solo action when consensus is required
  • ❌ Ignore minority opinions
  • ❌ Let proposals languish without voting
  • ❌ Make personal attacks

Decision Record

All decisions are recorded in .god/council/decisions/ with this structure:

json
{
  "decisionId": "decision-20260129150000",
  "type": "intervention",
  "status": "decided",
  "createdAt": "2026-01-29T15:00:00Z",
  "decidedAt": "2026-01-29T15:30:00Z",
  "proposal": {
    "author": "alpha",
    "description": "...",
    "rationale": "..."
  },
  "votes": {
    "alpha": {"vote": "approve", "comment": "...", "timestamp": "..."},
    "beta": {"vote": "approve", "comment": "...", "timestamp": "..."},
    "gamma": {"vote": "abstain", "comment": "...", "timestamp": "..."}
  },
  "quorum": 2,
  "result": "approved",
  "executedAt": "2026-01-29T15:35:00Z"
}

After Consensus

Once a decision is reached:

  1. If Approved: Execute the proposed action
  2. If Rejected: Document why and any alternatives
  3. Update Timeline: Log the decision event
  4. Notify Stakeholders: If relevant to execution layer
bash
# After approved decision
./scripts/god/observer.sh event "decision" "Proposal approved: DESCRIPTION"

# Execute the action
[perform the approved action]

# Mark as executed
jq '.executedAt = "'"$(date -u +%Y-%m-%dT%H:%M:%SZ)"'"' \
  .god/council/decisions/DECISION_ID.json > tmp && mv tmp .god/council/decisions/DECISION_ID.json

© YougLin-dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/god-consensus of YougLin-dev/Aha-Loop.

Open the folder on GitHubat commit 8d799b2

Compare with similar skills

God Consensus next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

God Consensus compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
God Consensus this skillYougLin-dev/Aha-Loop181—~2kAutomated safety check: PassMIT
Doc Coauthoringaws-samples/sample-strands-agent-with-agentcore19541 repos~3.2kAutomated safety check: PassMIT
Audit Onboarding Proposalhoangnb24/repository-harness1.2k—~4kAutomated safety check: PassMIT
No Negative EchoLB623/no-negative-echo897—~965Automated safety check: PassMIT
GEO Service Proposal Generatorzubair-trabzada/geo-seo-claude11k—~3kAutomated safety check: NotesMIT
Architectural ProposalsFritzAndFriends/SharpSite1452 repos~1.6kAutomated safety check: PassMIT

Similar skills

  • Doc Coauthoring

    aws-samples/sample-strands-agent-with-agentcore

    Official

    Guide users through a structured workflow for co-authoring documentation.

    195 GitHub starsUsed in 41 repos~3.2k tokens
    Sales & SupportAuto-check passed

  • Audit Onboarding Proposal

    hoangnb24/repository-harness

    Use only when the user explicitly invokes $audit-onboarding-proposal.

    1.2k GitHub stars~4k tokensUpdated 5 days ago
    Sales & SupportAuto-check passed

  • No Negative Echo

    LB623/no-negative-echo

    Prevent 此地无银三百两式 residue: finalize artifacts without echoing rejected session-only alternatives into labels, metadata, commits, PRs, or handoffs.

    897 GitHub stars~965 tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed

  • GEO Service Proposal Generator

    zubair-trabzada/geo-seo-claude

    Builds a client-ready AI-search-optimization proposal from an existing GEO audit, with pricing tiers, an ROI estimate and a markdown document ready to send.

    11k GitHub stars~3k tokensUpdated today
    Sales & SupportAuto-check: notes

  • Architectural Proposals

    FritzAndFriends/SharpSite

    How to write comprehensive architectural proposals that drive alignment before code is written

    145 GitHub starsUsed in 2 repos~1.6k tokens
    Sales & SupportAuto-check passed

  • Counter Proposal Generator

    zubair-trabzada/ai-legal-claude

    Generates specific counter-proposals for every unfavorable clause, with replacement language, negotiation talking points, and a ready-to-send email template

    1.8k GitHub stars~2.4k tokensUpdated 6 mo ago
    Sales & SupportAuto-check passed

More from YougLin-dev/Aha-Loop

All 15 skills in this repo

  • Architect

    YougLin-dev/Aha-Loop

    Designs system architecture and selects technology stack based on vision analysis.

    181 GitHub stars~2.2k tokensUpdated 8 mo ago
    Auto-check passed

  • Doc Review

    YougLin-dev/Aha-Loop

    Reviews and cleans up outdated documentation. An agent skill from YougLin-dev/Aha-Loop.

    181 GitHub stars~1.5k tokensUpdated 8 mo ago
    Auto-check passed

  • God Intervention

    YougLin-dev/Aha-Loop

    Guides God Committee members through executing interventions.

    181 GitHub stars~2.3k tokensUpdated 8 mo ago
    Auto-check passed

  • God Member

    YougLin-dev/Aha-Loop

    Defines God Committee member behavior and responsibilities with oversight authority.

    181 GitHub stars~1.6k tokensUpdated 8 mo ago
    Auto-check passed

  • Parallel Explore

    YougLin-dev/Aha-Loop

    Guides parallel exploration of multiple implementation approaches using git worktrees.

    181 GitHub stars~1.9k tokensUpdated 8 mo ago
    Auto-check passed

  • Plan Review

    YougLin-dev/Aha-Loop

    Reviews and adjusts PRD plans based on research findings. An agent skill from YougLin-dev/Aha-Loop.

    181 GitHub stars~1.8k tokensUpdated 8 mo ago
    Auto-check passed

Categories

Questions about God Consensus

What does God Consensus do?

Guides God Committee members through consensus-building for collective decisions. God Consensus is an agent skill from YougLin-dev/Aha-Loop. Guides God Committee members through consensus-building for collective decisions.

When should I use God Consensus?

God Consensus fits situations like: disagreement resolution; committee decision.

How do I install God Consensus in Claude Code?

Run `npx skills add YougLin-dev/Aha-Loop --skill god-consensus -a claude-code`. Or copy the skill folder (.agents/skills/god-consensus in YougLin-dev/Aha-Loop) into .claude/skills/god-consensus in your project. Claude Code loads it when a task matches its description.

How do I install God Consensus in Codex?

Run `npx skills add YougLin-dev/Aha-Loop --skill god-consensus -a codex`. Or copy the skill folder (.agents/skills/god-consensus in YougLin-dev/Aha-Loop) into .agents/skills/god-consensus in your project. Codex loads it when a task matches its description.

Can I use God Consensus in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add YougLin-dev/Aha-Loop --skill god-consensus -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/god-consensus, .gemini/skills/god-consensus, .github/skills/god-consensus and .opencode/skills/god-consensus in your project.

What does God Consensus need to run?

Going by SKILL.md and its folder, God Consensus needs the command-line tools its instructions call (jq).

Does God Consensus access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is God Consensus safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does God Consensus use?

God Consensus is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does God Consensus use?

About 2k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to God Consensus?

Skills that share tags, products or a category with God Consensus: Doc Coauthoring (aws-samples/sample-strands-agent-with-agentcore, 195 stars), Audit Onboarding Proposal (hoangnb24/repository-harness, 1.2k stars), No Negative Echo (LB623/no-negative-echo, 897 stars) and GEO Service Proposal Generator (zubair-trabzada/geo-seo-claude, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains God Consensus?

YougLin-dev (a GitHub user) maintains it in YougLin-dev/Aha-Loop, which has 181 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on February 3, 2026.

Source: YougLin-dev/Aha-Loop on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.