Council Skill 安全审计

78Use this skill to coordinate multiple subagents investigating the same question, with different models first and different assigned perspectives second, then synthesize their reports into one recommendation.910This skill is best for judgment-heavy tasks: architecture tradeoffs, risky bug fixes, code review red-teaming, rollout decisions, incident analysis, and “is this alternative worth pursuing?” questions.11

8788Compare the reports by evidence quality, not by vote count. In the final answer:8990- lead with the recommendation;91- call out consensus and disagreements;92- explain why the recommended option wins against the decision criteria;93- explicitly address the user’s stated concern;94- include relevant file paths/symbols without overloading the answer;95- distinguish “do now” from optional future hardening;96- mention confidence and material unknowns.97

2829Preferred default roster for a three-member council:3031- Opus 4.7 or the strongest available Claude/Opus reasoning model: architecture, correctness, and edge-case analysis.32- GPT 5.5 or the strongest available GPT/Codex model: implementation-grounded review, feasibility, and test strategy.33- An open-source model such as Kimi 2.6, GLM 5.1, or the strongest available OSS/local model: contrarian critique, hidden assumptions, and alternative framing.3435If one of these exact models is unavailable in the active harness, use the closest available model from that family and note the substitution. If no open-source model is available, use a third distinct frontier model if possible; otherwise use the strongest remaining model with a deliberately adversarial or specialist angle.36

4748For read-only investigations, keep all children in the same checkout and explicitly tell them not to edit files. For implementation or prototyping councils, give each local child its own git worktree and branch so they cannot collide.49

126127- If the council is read-only, tell children not to modify files, commit, create branches, or open PRs.128- If the council involves PR or branch work, follow the repository’s normal version-control rules and use isolated worktrees for parallel local edits.129- If the council is about code review feedback, mark review comments resolved only after the underlying issue is actually addressed.130- Do not expose internal child agent IDs in user-facing summaries unless the user explicitly asks for them.

2name: council3description: Run a model-diverse subagent council to investigate the same problem from multiple perspectives, compare findings, and produce a final recommendation. Use this skill whenever the user asks for a council, second opinions, multiple agents/models to evaluate one question, parallel investigation, red-team/blue-team comparison, or help deciding between competing technical approaches.4---

5152For explicit orchestration requests, briefly tell the user which council members you plan to launch and what each will investigate, then wait for approval before calling `run_agents`.53