control-tower-plugins

Take a finished change from working diff to a ready-for-review PR, ending with the PR URL as plain text. Use when the user says "ship it" or wants to go from a working change to an opened PR.

Commit the current change, push a branch, and open a draft PR. Use when the user wants to open a PR for finished work.

How to drive the `ct` CLI to run matches and produce every number and graph a control experiment ships. Covers `ct run eval`, `ct run monitor`, `ct run summarize`, `ct game-metrics metrics / graph roc / graph pareto`, `ct traj`, and the viewers. Load this when you launch a match, compute safety or usefulness, regenerate a graph, or need the exact reproduce command for an output. White loads it always; main and others load it on demand.

The empirical-research method and quality bar for AI-control experiments run through the ct CLI. Reduce uncertainty fast, iterate on qualitative plus quantitative evidence, size for power, keep splits clean, report honestly, and hold P1 observability, P2 affordance discipline, and the per-team B/R/W/M criteria. Loaded by every role.

The public, LessWrong-style writeup of a control experiment. Ruthlessly compressed for a reader with zero context, leading with the surprise, citing public-viewer trajectory URLs only. Load this in the writing phase when producing the shipped post into `outputs/`. It lifts the STRONG-tagged claims from the internal [report-writing]; same evidence base, far less detail. Before shipping it runs the lw-review gate below.

The red (attacker) role for ONE protocol in an automated control-research run. Load this when you are spawned as red_<protocol>. Holds red's self-managed loop, guarded objective, iteration discipline, and validity rules. Every shared fact (folder layout, iteration mechanics, the stop gate, the game, safety formula, the quality bar, ct commands) lives in a general skill and is referenced here by name, never copied.

The white (referee) role for ONE protocol in an automated control-research run. Load this when you are spawned as white_<protocol>. Holds white's self-managed loop, guarded objective, task-set ownership, validity disciplines, and per-protocol stopping judgment. Every shared fact (folder layout, iteration mechanics, the stop gate, the game, safety formula, the quality bar, ct commands) lives in a general skill and is referenced here by name, never copied.

The discipline that makes a multi-hour control run actually finish instead of stalling or quitting early. It keeps going, get unstuck, fix problems, self-review before you report. Loaded by every agent to keep it going.

The interactive entry point for an automated control research run, loaded by main. Use when a human says "start an automated control research session" (or similar). Runs the questionnaire, helps write proposal.md, waits for "start", then bootstraps the folder, brings up the dashboard, spawns the team, writes the predicted-results preview into outputs/ while waiting on teammates, and drives the loop.

The single home for how a control experiment is organized on disk and how a protocol is iterated to its stopping point. Loaded by blue, red, white, and the judge. Covers the folder layout, one-knob iteration, move order, convergence, the smoke gate, and the per-protocol stopping condition.

Take a request — a Linear issue or a feature description — all the way to a reviewed, ready PR: triage it, work out the right approach, propose it for a quick OK, implement, then ship. Use when the user wants the agent to plan and build something end to end.

Watch an open PR until it's clean — poll CI, address bot comments, hide each bot comment as it's handled, then mark ready for review. Use when the user wants a draft PR monitored through to green.

The blue (defender) role for ONE protocol in an automated control-research run. Load this when you are spawned as blue_<protocol>. Holds blue's self-managed loop, guarded objective, iteration discipline, and validity rules. Every shared fact (folder layout, iteration mechanics, the stop gate, the game, safety formula, the quality bar, ct commands) lives in a general skill and is referenced here by name, never copied.

The domain reference for AI control research, loaded by every role. The blue/red/white game, trusted/untrusted/human, honest vs attack evals, the safety and usefulness metrics, trusted monitoring and the other protocols. The deeper source is https://github.com/linuxarena/control-tower/blob/main/docs/control-concepts.md.

The judge role, an ephemeral read-only subagent main spawns per protocol at phase boundaries and on demand to grade that protocol against its proposal and the shared quality bar. Load this when you are spawned as the judge. Holds the grading procedure, the game-tree-completeness walk, the grade.md format, and the recompute-and-verify disciplines. Shared facts live in the general skills, referenced here by name.

Structured process for a literature review, search strategy, source vetting, and synthesis. Use when asked to review existing work on a control-research topic (prior protocols, attacks, monitors, safety results). Not for incidental background reading during a run.

The internal, hypothesis-graded per-protocol report. One report per protocol at `outputs/reports/<protocol>.md`, capturing everything that protocol's team tried and why, qualitatively and quantitatively, with a support tag on every claim and a runs table of every run inside the report so nothing is lost. Load this in the writing phase when synthesizing a protocol's matches into its report. This is the internal tier; the public post is [post-writing].

The trajectory-analysis role, an ephemeral single-invocation subagent any team member spawns to autopsy specific run trajectories against one investigation question. Load this when you are spawned for a trajectory autopsy. Holds the bounded autopsy procedure, the RED FLAGS checks, and the write-into-the-caller's-dir rule. Shared facts live in the general skills, referenced here by name.