leek/agent-skills / skills/panel
panel
VerifiedConvene a panel of agent CLIs (grok, claude, codex, agy) on a prompt or a code review, then report one consensus grouped by how much they agree.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.3 KB |
| agents/openai.yaml | config | 245 B |
| references/cli-invocations.md | markdown | 4.9 KB |
| references/panelist-brief.md | markdown | 2.0 KB |
| references/review-shape.md | markdown | 2.0 KB |
| scripts/launch.shexecutable | script | 1.8 KB |
references/cli-invocations.md
View on GitHub# Panel CLI invocations
Per-CLI detail behind [`scripts/launch.sh`](../scripts/launch.sh), which holds the one
canonical headless command for each CLI. Read this only when a CLI misbehaves, when you
want a hard read-only guarantee, or when the panel roster changes; a roster change is a
new `case` in that script plus a section here.
Three rules hold for every CLI:
- **No `--model`.** Each CLI must run as its own latest/default model.
- **The task reaches each CLI from the file.** On stdin (`claude`, `codex`), by
`--prompt-file` (`grok`), or, for `agy`, read by the script and passed as one argument
(bash quotes it, so a backtick or `$` in the task stays text). A CLI that does not read
the task on stdin gets `< /dev/null`, so it does not block there. The panelist's own
command stays literal, which is what worktree isolation needs.
- **Headless needs auto-approval.** A headless run cannot answer a permission prompt, so
each command carries that CLI's bypass flag. The read-only options below vary in
quality; the working-tree check in `SKILL.md` step 3 (not a flag) is what enforces
review-only.
## claude
- Headless: `-p` / `--print` runs one prompt and exits. With no prompt argument it reads
the prompt from stdin, which is how the script passes the task file.
- Auto-approve: `--dangerously-skip-permissions`.
- Read-only variant: keep `--dangerously-skip-permissions` (so it stays non-interactive)
and drop the edit tools: `--disallowedTools Edit Write NotebookEdit`. Those three are
the real tool names: `MultiEdit` is not one and triggers a warning.
- Structured output: `--output-format json` (default is text, which the subagent distills).
## codex
- Headless: the `exec` subcommand is non-interactive.
- Working dir: `-C` / `--cd <dir>`: the script passes the directory it runs from, so
codex reads the right repo.
- Auto-approve: `--dangerously-bypass-approvals-and-sandbox`.
- Read-only variant: `codex exec --sandbox read-only --cd <worktree> - < <task file>`: the
`read-only` sandbox blocks writes while still running non-interactively. Drop the
bypass flag when you use it; the two are mutually exclusive.
- Prompt position: trailing positional, after all flags. `-` (or no prompt) reads the
prompt from stdin.
- Structured output: `--output-schema <file>` plus `-o` / `--output-last-message <file>`.
## agy
- Headless: `-p` / `--print` runs one prompt and exits. It has no prompt-file flag, and
`-p` with no value prints help rather than reading stdin (stdin is read only with
`--input-format stream-json`), so the script passes the task text as `-p`'s value.
- **Always pass `--print-timeout 30m`.** The default is 5m, and a code review takes longer
than that, so without it agy dies with `Error: timeout waiting for response` after five
minutes and the seat returns nothing. Put it before `-p` like every other flag.
- Flag order: `-p` / `--print` consumes the NEXT token as its prompt value, so put every
other flag **before** `-p` and give the task as `-p`'s value last,
`agy --dangerously-skip-permissions -p '<task text>'`. Putting `-p` first (`agy -p
--dangerously-skip-permissions '<task text>'`) makes it swallow `--dangerously-skip-permissions`
as the prompt: the flag is silently dropped (permissions never skipped) and the real
task is discarded as an ignored trailing positional, so no review runs.
- Auto-approve: `--dangerously-skip-permissions`.
- Read-only: agy has no clean review read-only flag. Do **not** use `--mode plan` for a
review: plan mode hijacks the run into "planning mode" and ignores the task. Keep
auto-approve and rely on the working-tree check in `SKILL.md` step 3.
- Structured output: `--output-format json` and `--json-schema <schema>`.
## grok
- Headless: `-p` / `--single <PROMPT>` runs one prompt and exits; `--prompt-file <PATH>`
does the same with the prompt read from a file, which is how the script passes the task.
- Auto-approve: `--always-approve`.
- Read-only variant: grok has `--sandbox <profile>` (also `GROK_SANDBOX` env) plus
`--deny <rule>` permission rules. Run `grok --help` for the profile names on this
machine before relying on one; they are grok-specific and not fixed here.
- Structured output: `--json-schema <schema>` (implies `--output-format json`).
## Absent vs errored
- **Absent**: `command -v <cli>` prints nothing. Drop the CLI from the run and name it
in the report. Absent CLIs never count toward the consensus grades.
- **Errored**: the CLI is installed but the run failed: non-zero exit, empty output, an
auth error, or a timeout. The subagent returns `status: errored` with the one-line
cause. An errored CLI also does not count toward the grades, but the report names it so
the user knows the panel was short a voice.
## Auth
Each CLI authenticates on its own (its own login, API key, or config). The panel does not
manage credentials. An auth failure surfaces as an `errored` result, not a crash.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |