Clixad
Freemium
Developers who prefer terminal workflows
A single model pass on a hard coding task ships green tests that hide logic bugs — because the thing writing the code is the same thing checking it. pantheon-skills breaks that loop by running the task through multiple independent implementations, then pointing a separate agent at the result with explicit instructions to break it.
The harness follows a fixed pipeline: plan, then N parallel implementations, then adversarial verification, then a judge that decides which survives. A companion pair — pantheon-gap and pantheon-gap-x — runs the same shape as a reviewer against an existing codebase, surfacing what's missing rather than building something new. The cross-model variant (pantheon-x, pantheon-gap-x) routes the verification step through GPT-5.5, so the reviewer isn't the same model family as the builder. This is a Claude Code skill, not a standalone app — it lives inside your Claude Code environment, which means setup assumes that context and breaks outside it. The repo is early-stage, with ten commits and no open issues, so production edge cases land entirely on you.
Bottom line: Pick this when you need a repeatable adversarial review loop for a coding task you can express as tests — skip it if you don't have a paid Claude Code plan or need a tool that runs outside that environment.
Find your fit
More options in CLI Coding Agents. Compare pricing, platforms, and features side by side.
Freemium
Developers who prefer terminal workflows
Freemium
Developers preferring fully local agent execution
Single-model code generation has a structural blind spot: the model that writes the solution also evaluates it, so confident wrong answers pass its own review. pantheon-skills addresses this by packaging a plan → N parallel implementations → adversarial verification → judge pipeline as Claude Code skills. You invoke the skill inside Claude Code, the harness spins up multiple implementation attempts in parallel, a separate agent tries to break each one against the stated requirements, and a judge picks the survivor. The gap variants (pantheon-gap, pantheon-gap-x) apply the same harness to an existing project — pointing the reviewer at your codebase to report what’s missing rather than producing new output.
The differentiating feature is the cross-model verification path. pantheon-x and pantheon-gap-x route the adversarial review step through GPT-5.5, so the agent trying to break the implementation is from a different model family than the agent that built it. The vendor describes this as catching bugs a single pass ships green — the value is specifically in the independence of the reviewer, not in either model being individually stronger.
This tool fits teams already inside the Claude Code ecosystem who want a harness for correctness-critical tasks that can be expressed as tests. The pipeline is explicitly scoped to tasks where you can define a verification condition — it does not help with tasks where correctness is subjective or hard to specify. The repo carries an MIT license and is self-hostable, but it is not a standalone service: it runs as a Claude Code skill, which requires a paid Claude Code plan. Teams without that plan have no supported path in.
The project is a public GitHub repo at an early commit count. There is no API, no hosted version, and no documented integration surface outside Claude Code. The gap-analysis variants add a second use case shape but follow the same architectural constraints — plan, implement, verify, judge — applied to review rather than creation.
Sign in to rate this tool or suggest an edit.