Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
68 changes: 68 additions & 0 deletions agents/yogirk__agent-council/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,68 @@
# Agent Council

**Convene a panel of CLI-based AI agents to deliberate on your hardest engineering questions.**

Agent Council orchestrates Claude Code, Codex CLI, and Gemini CLI through a structured
three-stage deliberation — independent opinions, peer review, and chairman synthesis — then
delivers a verdict with consensus mapping, divergence analysis, and a confidence score.

## What makes it different

Every existing LLM council is API-based (pass text, get text back). Agent Council is
different: council members are **CLI agents with tool access**. They can grep your codebase,
read migration files, and run `git log` before opining. Opinions are grounded in your
actual project, not abstract text generation.

You're also tapping into **subscriptions you already have** — no new API tokens required.

## Key Capabilities

- **`/council "question"`** — Dispatch all agents in parallel, collect independent opinions, synthesise as chairman
- **`/council --with-review`** — Add a Stage 2 peer-review round before synthesis
- **`/council --quick`** — Skip peer review for fast turnaround
- **`/council-list`** — List all past deliberation sessions
- **`/council-replay <session>`** — Replay a past session in the terminal
- **`/council-revisit <session>`** — Re-run deliberation with current project context ("living decisions")
- **`/council-outcome <session> "result"`** — Record what actually happened to close the loop
- **`/council-nudge <session> --agent codex --correction "..."`** — Dispatch a targeted Stage 4 correction to a single agent

## Example

```
/council "Should we use Postgres or DynamoDB for our event sourcing system?"
```

```
Stage 1 complete: 3/3 successful opinions

--- CHAIRMAN SYNTHESIS (claude) ---

Consensus: All agents agree — Postgres is the right choice given strong
consistency requirements and team SQL experience.

Divergence: Claude emphasises ACID guarantees. Codex flags a 10TB scaling
ceiling without sharding. Gemini suggests read replicas as a scaling bridge.

Confidence: HIGH — Strong consensus across models.
```

## Installation

```bash
npx cliagent-council
```

Or manually:

```bash
git clone https://github.com/yogirk/agent-council.git
cd agent-council && ./setup
```

**Requirements:** [Bun](https://bun.sh) + at least 2 of: Claude Code, Codex CLI, Gemini CLI.

## GitAgent Protocol

This agent ships with `agent.yaml` + `SOUL.md` at the repo root, making it fully
[GAP-compliant](https://gitagent.sh). Run it on any compatible runtime or list it
in the [Open GAP registry](https://registry.gitagent.sh).
15 changes: 15 additions & 0 deletions agents/yogirk__agent-council/metadata.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
{
"name": "agent-council",
"author": "yogirk",
"description": "Convenes a panel of CLI AI agents (Claude, Codex, Gemini) to deliberate on engineering questions via structured multi-stage discussion and chairman synthesis.",
"repository": "https://github.com/yogirk/agent-council",
"path": "",
"version": "0.3.3",
"category": "developer-tools",
"tags": ["multi-agent", "deliberation", "claude-code", "codex", "gemini-cli", "engineering-decisions", "code-review", "architecture"],
"license": "MIT",
"model": "claude-sonnet-4-5-20250929",
"adapters": ["claude-code", "system-prompt"],
"icon": false,
"banner": false
}