second-opinion

so is a single CLI for getting second opinions from other AI models. It works through the agent CLIs you already have, so each call uses your existing subscriptions instead of API keys:

You can call it from any harness. An agent runs so ask, the prompt goes out to a profile (one model, or a panel answering in parallel), and a chair model synthesizes the panel’s answers. A mode fixes the response structure, for example a code-review format.

Install

curl -fsSL https://raw.githubusercontent.com/peter-olom/second-opinion/main/install.sh | sh
so skill install          # teach Claude Code, Codex, and pi to use so

Then ask your agent for a second opinion. On first use it will set up profiles with you (see Profiles).

The script downloads the release for your OS and architecture, verifies its checksum, and installs to ~/.local/bin. You can set SO_VERSION=v0.1.0 to pin a release, or SO_INSTALL_DIR to install somewhere else. Windows builds are available as zips on the releases page.

so skill install writes the agent skill into the skills directory of every harness it finds: ~/.claude/skills, ~/.codex/skills, and ~/.pi/agent/skills. Name harnesses to limit it (so skill install claude), or add --dir for other skill directories. Re-run it after upgrading so to refresh the skill.

Uninstall

so uninstall          # removes the skill files, run history, and the so binary; keeps your config
so uninstall --all    # also removes the config file in use (--config or $SECOND_OPINION_CONFIG)

It lists what it will remove and asks before deleting (--yes skips the prompt). Some details:

• It deletes only files so manages: each second-opinion/SKILL.md (that skill folder belongs to so; so skill install overwrites it and refuses to write through a symlink), the runs/*.json files, the binary, and with --all the config file. Folders are removed only if that leaves them empty. Anything you added stays, and so does a config that shares a folder with the history.
• It leaves symlinked folders alone, and never removes a folder that one of them points to, so no link is left dangling. To be safe, with --all it also keeps the config’s folder (even if empty) when the config path is relative, contains . or .., or when the config’s own folder is a symlink.
• If you run so through a symlink, only the link is removed. The file it points to stays. If you run the binary itself, any so links on your PATH that point to it are removed too, so none is