跳到主要内容
知仓学习社ZHICANG

llm-council

Provider-agnostic multi-LLM deliberation. Three phases — independent responses, cross-model anonymized ranking, chairman synthesis. Provider config …

读凭据写文件读文件联网严重 0 · 高危 3rohitg00/pro-workflow

它会碰到什么

扫了多少2 个文本文件,15 KB
它会碰到什么读凭据写文件读文件联网
命中总数14 处
命中统计严重 0 · 高 3 · 中 7 · 低 4
逐条看命中(3 条严重或高危)
  • scripts/council.js:45cred-envread
    baseUrl: process.env.LLM_COUNCIL_BASE_URL || '',
  • scripts/council.js:46cred-envread
    defaultModels: (process.env.LLM_COUNCIL_MODELS || '').split(',').filter(Boolean),
  • scripts/council.js:47cred-envread
    defaultChairman: process.env.LLM_COUNCIL_CHAIRMAN || '',

这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。

技能内容

LLM Council

Karpathy's LLM Council pattern, provider-agnostic. dair-academy's version hardcoded Fireworks; ours reads any OpenAI-compatible endpoint via env.

When to use

  • High-stakes plan review (/plan crosses N-file threshold)
  • Conflicting learning-rules → re-resolve via vote
  • User invokes /council "<query>" or /wiki council
  • Architecture decisions where you want multiple viewpoints captured
  • Persisting deliberation as a wiki page for future reference

Three phases

  1. Independent: each model answers in parallel
  2. Ranking: each model ranks anonymized peer responses
  3. Synthesis: chairman model reads all responses + rankings → final answer

Provider config

Provider chosen via env. First-match wins:

| Env var | Provider | Default base URL |

|---------|----------|------------------|

| ANTHROPIC_API_KEY | Anthropic | https://api.anthropic.com |

| OPENAI_API_KEY | OpenAI | https://api.openai.com/v1 |

| OPENROUTER_API_KEY | OpenRouter | https://openrouter.ai/api/v1 |

| FIREWORKS_API_KEY | Fireworks | https://api.fireworks.ai/inference/v1 |

| LLM_COUNCIL_BASE_URL + LLM_COUNCIL_API_KEY | Custom OpenAI-compat | (user-supplied) |

Override per-run with --provider openai|anthropic|openrouter|fireworks|custom.

Default model rosters per provider live in scripts/council.js and can be overridden via --models CSV and --chairman <id>.

Commands

node $SKILL_ROOT/scripts/council.js run "<query>" [--models id1,id2,id3] [--chairman id] [--provider <name>] [--wiki <slug>]
node $SKILL_ROOT/scripts/council.js providers
node $SKILL_ROOT/scripts/council.js show <session-id>

--wiki <slug> writes the full transcript to <wiki>/derived/council/<session-id>.md and registers it via wiki-cli.js page so it shows in FTS5 search.

Output

Each session writes:

~/.pro-workflow/council/<session-id>/
├── config.json           # query, models, chairman, provider
├── phase1_responses.json # raw API responses per model
├── phase2_rankings.json  # anonymized ranking outputs
├── phase3_synthesis.txt  # chairman's final answer
└── final_output.md       # human-readable bundle

Console prints the markdown bundle. Pipe to pbcopy / tee as needed.

Hard rules

  1. Never skip the ranking phase. It's the core of the council pattern.
  2. Save raw responses to disk verbatim. No summarization in storage.
  3. Anonymize responses for ranking — models see Response A/B/C/..., not peer names.
  4. The chairman sees both real names AND rankings.
  5. Display all three phases to the user. No phase elision.

Cost awareness

The script logs per-call latency + tokens on supported providers. Multiply by your provider rate to estimate. Council cost grows linearly with len(models)^2 (each model ranks all others) plus the chairman.

Default council size: 3-5 models. More models = exponentially more ranking calls.

Use with wiki

/wiki council agent-memory "should we adopt episodic memory in our agents?"

Loads agent-memory wiki context as system prompt prefix, runs council, persists transcript as wiki/derived/council/<id>.md. The transcript becomes searchable via /wiki ask.

想直接用这个技能?

本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。

它属于哪个仓库

星标★ 2,870
本站分层T1
该仓技能数41
原文件路径skills/llm-council/SKILL.md

同一个仓库里的其他技能

看这个仓库的全部 41 个技能