Second Opinion
Query one independent CLI peer or a bounded named review panel for plans, PRs, code, or bugs.
quorum and consensus execute the same enabled routes from the selected panel exactly once. Quorum
uses the profile's successful-route threshold; consensus interpretation additionally requires its
unique-provider threshold. Agreement and vote count never establish correctness.
Usage
/second-opinion
/second-opinion review-pr 123
/second-opinion validate-plan "<plan>"
/second-opinion triage-bug "<description>"
/second-opinion ask "<question>"
# One independent route
/second-opinion ask "..." --agent peer # explicit/default independent peer
/second-opinion ask "..." --agent claude
/second-opinion ask "..." --agent claude --effort xhigh
/second-opinion ask "..." --agent codex
/second-opinion ask "..." --agent gemini
/second-opinion ask "..." --agent codex --model <id>
# Policy-neutral named panels
/second-opinion review-pr --agent quorum # defaults to focused
/second-opinion validate-plan "..." --agent consensus # defaults to extreme
/second-opinion review-pr --agent consensus --panel large
/second-opinion ask "..." --agent quorum --panel large \
--route-model claude-fable=opus --route-effort claude-fable=max
--timeout <minutes> defaults to 10 and is capped at 30.
Requirements
- Single/local routes: the selected
claude,codex, orgeminiCLI installed and authenticated. - Panel orchestration:
jqplusscripts/review-panel.sh. - OpenRouter subset only:
curl, plus eitherOPENROUTER_API_KEYorsecret-api-keywithSECRET_API_KEY_PROJECT, and a configured panel/profile in~/.agents/second-opinion/config.json. Optional exact-modelmodelPoliciesin that user-local file may setconsent: "allow"; absent or invalid policies remain confirmation-required. - PR context:
gh, Python 3.10+, and the installedreview-pr/scripts/gh-pr-snapshot.pycollector. Missing/partial/stale evidence stops PR dispatch; local routes also require a proven invoking checkout. Read PR evidence and stale-safety for every PR invocation.
Read references/review-panels.md when quorum or consensus is
selected. If the selected panel contains OpenRouter routes, also read
references/openrouter-consensus.md completely before executing.
Model/effort precedence is in
references/external-model-resolution.md.
Model independence and cost
A second opinion should come from a different vendor than the model that produced the work:
- Claude session → Codex first, then Gemini.
- GPT/Codex session → Claude first, then Gemini.
- Other session → the best available independent Claude or Codex route.
peer is the explicit name for this selection and is also the no---agent default. Direct
claude, codex, and gemini remain supported.
Prefer subscription/OAuth routes for one peer. Treat API-key/BYOK and unknown-cost direct routes as
metered and obtain current-run consent before invocation. A named panel does not infer billing from a
provider name. Its configured local routes are the approved local subset; every OpenRouter route is a
separately metered subset unless an exact user-local modelPolicies entry explicitly sets
consent: "allow".
For a direct single agent only:
- no
--model→ when the resolved route is Claude, use the skill defaultopus; Codex and Gemini retain their CLI-native defaults; --model smart→ retain the CLI-native default;--model fast→ use a verified CLI-native fast alias, otherwise retain and report the native default;--model <id>→ pass the literal ID through;--effort <level>→ for Claude only, pass the literal supported level (low,medium,high,xhigh, ormax) through; for Codex/Gemini, reject it and use their existing native controls.
For panels, generic --model is invalid. Use repeated --route-model ID=VALUE and
--route-effort ID=VALUE. OpenRouter identities cannot be overridden. Unsupported effort is rejected,
never translated.
1. Parse arguments
Extract:
- mode:
review-pr,validate-plan,triage-bug, orask; - target: PR URL,
owner/repo#number, current-repository shorthand, plan, bug description, or question; - PR-only optional
--expected-headSHA, passed unchanged to the shared collector; - agent:
peer,claude,codex,gemini,quorum, orconsensus; - panel: a local profile name;
- timeout: 1–30 minutes, default 10;
- direct model and optional effort, or repeated route-specific model/effort overrides.
Defaults and validation:
- no agent →
peer; quorumwith no panel →focused;consensuswith no panel →extreme;- reject unsupported agent names;
- reject
--panel,--route-model, or--route-effortfor a direct single agent; - accept direct
--effort low|medium|high|xhigh|maxonly for the Claude route; reject it for Codex/Gemini; - reject generic
--modelforquorumorconsensus.
If no mode is supplied, ask what to review. consensus must always be explicitly named; never infer
it from task risk, panel size, or an API key.
2. Gather and sanitize context
review-pr
Follow PR evidence and stale-safety completely: collect through the
review-pr authority, retain repo/node/head/base/state identity, sanitize one fixed packet, gate
local routes on the already-matching invoking checkout, and revalidate after opinions return.
No independent mutable metadata/diff collection or default-branch substitution is permitted.
A partial/stale/failed packet is not ready to send. Missing local checkout proof makes local routes unavailable, not permission to read the workspace. Final validation failure yields no current PR assessment; preserve original opinions only as stale/unvalidated evidence. This skill supplies independent claims, never a merge verdict, publication, requirements sign-off, or automatic fixes.
validate-plan
git ls-files | head -100
Ask for feasibility, completeness, dependencies, risks, and simpler alternatives, followed by the plan.
triage-bug
Ask for likely root causes, relevant components, investigation steps, falsification tests, and potential fixes, followed by the bug description.
ask
Pass the question with current-repository context.
For every mode, remove secrets, credentials, .env contents, private keys, and irrelevant personal
data. Never silently truncate oversized context; summarize before route selection and say so. Local CLI
routes are read-only repository reviewers and may inspect files in the current repository, so use
them only when that repository's readable contents are safe to share with those providers. For PR
mode, the stricter verified-cwd eligibility and final revalidation contract above is mandatory. OpenRouter receives the sanitized prompt as its user message plus a fixed, non-secret completion
contract; it receives no tools or repository access.
3. Execute one peer/direct agent
Resolve peer using the independence rule, then invoke exactly one eligible route. Pass the actual
assembled packet without allowing writes. PR mode must pass its just-in-time local preflight first;
an unavailable route is not permission to substitute another provider or cwd.
Claude
claude -p "{assembled_prompt}" --tools "Read,Grep,Glob" --model {resolved_model} --effort {resolved_effort}
Without --model, resolve {resolved_model} to opus; --model smart instead omits the flag and
retains the Claude CLI-native default. Pass every other resolved model as --model <id>. When
--effort is supplied, pass it through to Claude Code; when omitted, preserve the CLI-native
setting and report native-default.
Codex
All modes, including PR review, use the assembled packet rather than a branch-based native review:
codex exec --sandbox read-only {exec_model_flag} "{assembled_prompt}"
For codex exec, {exec_model_flag} is --model <id> for an explicit resolved model and empty for
the native default.
Gemini
gemini -p "{assembled_prompt}" --sandbox -o text {model_flag}
Apply the parsed timeout. If the route fails or times out, preserve the error and offer another independent direct route; never retry or substitute silently.
4. Execute a named panel
Use the same exact sanitized user prompt for every route. The OpenRouter helper adds only its fixed
completion contract as a system message. Create a private file with mktemp, set mode 600, and write
the prompt with Write. Do not put panel prompt text in shell argv.
4.1 Check and bind
~/.agents/skills/second-opinion/scripts/review-panel.sh check \
--panel {panel_name} \
--prompt-file {prompt_file} \
{repeated_route_overrides}
Retain and display:
- ordered route IDs, kinds, providers, roles, availability, effective model/effort, and provenance;
- configured quorum and consensus thresholds, enabled/disabled routes, and limits, including fixed OpenRouter completion-contract bytes;
panelSha256,openrouterSha256, andpromptSha256.
If profile validation fails, stop before any route invocation. Missing route prerequisites degrade the panel; they do not authorize substitution.
4.2 Run the local subset
~/.agents/skills/second-opinion/scripts/review-panel.sh run-local \
--panel {panel_name} \
--prompt-file {prompt_file} \
--panel-sha256 {panelSha256} \
--prompt-sha256 {promptSha256} \
--timeout {timeout_seconds} \
{repeated_route_overrides}
For PR mode, perform the local preflight from the evidence contract immediately before this call. If the invoking checkout is ineligible, do not run the local subset; report its routes unavailable with the context reason and let evaluation preserve missing results. Never forge successful results.
Save the returned JSON array to a mode-private result file. The coordinator invokes each enabled local route at most once, in bounded parallel batches, with read-only tools/sandboxing and prompt stdin. Disabled routes are not invoked. Preserve missing CLIs, timeouts, and failures.
4.3 Decide the OpenRouter subset
If openrouter.requestCount == 0, skip this step.
If prerequisites are unavailable, make no request and allow evaluation to report those routes as
missing/unavailable. If openrouter.consentRequired is false, every selected route has an exact,
user-local consent: "allow" policy: invoke run-openrouter --configured-consent with all three
digests and the same profile, prompt, timeout, and overrides. Otherwise, immediately before requests
use one AskUserQuestion that discloses only the OpenRouter routes whose policies remain ask:
exact routes/models/vendors, request count, concurrency, prompt cap (including the displayed fixed
completion-contract bytes), output-token cap, timeout, variable pricing, and that OpenRouter credits
will be consumed.
- Approve → invoke
run-openrouter --confirmedwith all three digests and the same profile, prompt, timeout, and overrides. - Decline/ambiguous/abandoned → invoke
decline-openrouterwith all three digests. It generates explicit declined results and makes no network request.
Configured authorization is exact-model and user-local; it is never inferred from a provider, panel, prior approval, or spend. Interactive consent applies once and is never persisted. A panel, subset, prompt, or policy digest mismatch requires a new check and fresh consent. Never retry, substitute, or expand a metered subset.
4.4 Evaluate mechanical quorum
Write the check, local-result, and OpenRouter-result JSON to private files, then run:
~/.agents/skills/second-opinion/scripts/review-panel.sh evaluate \
--policy {quorum|consensus} \
--check-file {check_file} \
--results-file {local_results_file} \
--results-file {openrouter_results_file}
Omit a result file only when that subset did not run and produced no results. The evaluator preserves
panel order, reports disabled and unavailable routes, counts successful routes and unique successful
providers, reports same-provider corroboration, and evaluates quorumMet and consensusEligible
against their separate threshold units. OpenRouter routes count as successful only when they
return non-empty text with the fixed completion marker, normalized finish reason stop, and no tool
calls. The helper strips the marker and classifies every other transport-success response as
incomplete; this is protocol completion, not semantic validation. Results retain bounded response
ID/model/provider, normalized and native finish reasons, usage, and tool-call count, but never tool
arguments or hidden reasoning text. The evaluator deliberately does not compare natural-language
claims. Remove all private prompt/result files after evaluation, success or failure.
5. Present panel results
For PR mode, finish the PR evidence contract's final revalidation before this section or any single-route assessment. If it fails, show transport/quorum counts and responses only under their stale/unvalidated label; do not synthesize current evidence-backed agreements or PR conclusions.
First show every route faithfully:
## Review Panel: `{panel}` — {quorum|consensus}
| Route | Kind | Provider | Role | Model / effort | Status |
|---|---|---|---|---|---|
| ... |
**Quorum:** {successful routes}/{quorum required} — met / not met
**Provider coverage:** {successful unique providers}
For the consensus policy, add **Consensus threshold:** {successful unique providers}/{consensus required} — eligible / not eligible. Then include each successful response under its route heading and
every error, incomplete response, decline, or timeout under Unavailable routes. For an incomplete OpenRouter route, report its preserved
visible response and termination diagnostics without treating either as independent coverage.
Quorum policy
When quorum is met, present findings by route/provider without requiring agreement. When not met, state that quorum failed and identify unavailable routes. Do not relabel repeated claims as consensus.
Consensus policy
If consensusEligible is false, state no consensus assessment was made. Preserve returned
opinions but do not synthesize agreement, even when the lower ordinary quorum was met.
If eligible, compare claims and report all five categories:
- Evidence-backed agreements — independently supported claims, not repeated prompt premises.
- Disagreements / uncertainty — conflicting conclusions and unresolved evidence.
- Shared assumptions — repeated claims without independent support.
- Same-provider corroboration — explicitly separate from independent-provider agreement.
- Unavailable routes — missing, declined, failed, and timed-out perspectives.
Never convert a majority into correctness.
6. Repository-grounded assessment
For PR mode, complete the original-identity remote recheck and any required full local recheck in the PR evidence contract first. A failed check means no current PR assessment; show historical opinions with their stale/unvalidated status instead. Never assess against unrelated or moved cwd.
For eligible results, critically verify every material external claim against the supplied scope
and its matching repository evidence. Missing supporting context remains Uncertain, not a new search
scope. This is advisory claim validation, not verify-task coverage or review-pr merge clearance.
Present a concise assessment table:
### My Assessment
| # | Finding | Verdict | Evidence |
|---|---|---|---|
| 1 | ... | Valid / Non-issue / Already handled / Uncertain | file/path:line or reason |
List only genuinely actionable items. A unique, well-evidenced concern may outweigh repeated weak claims; repeated unsupported claims remain invalid.
Error handling and rules
- Never let any route modify files.
- Never send secrets or credentials to a route.
- Never expose OpenRouter credentials or place the bearer token in argv.
- Never give OpenRouter routes tools or repository access.
- Never invoke a disabled profile or route, retry/substitute a failed route, or silently change a configured panel.
- Always report effective OpenRouter consent policy and basis alongside route provenance.
- Always report effective route provenance; use
skill-defaultfor the implicit direct-Claudeopusselection andnative-defaultwhen the runtime does not reveal a concrete setting. - Preserve external responses faithfully before adding your own assessment; the OpenRouter transport completion marker is protocol metadata and is removed before presentation.
- Never count an
incompleteOpenRouter result toward quorum or describe the completion contract as semantic validation. - A partial panel is partial coverage, not a complete panel.