Plugin
debate
Structured multi-round debate between AI tools with proposer / challenger roles and a final verdict. `/debate` orchestrates a back-and-forth between two AI CLIs (Gemini, Codex, Claude Code, OpenCode, Copilot, Kiro) on a design decision, technical question, or contested approach. Each round, one tool proposes / defends and the other challenges; the orchestrator synthesizes the disagreement and renders a verdict with reasoning. Surfaces blind spots that single-tool consultation misses, especially on architectural decisions where two strong arguments exist. Programmatic entry point — other agents and workflows can spawn a debate via Task() to break a tie.
- Analysed
- Last observed
What the code does
- Runs shell commands Code that starts system commands on the machine it runs on.
- Starts other processes Code that launches separate programs.
- Evaluates code at runtime Code that builds and runs code while it executes.
- Runs an AI coding agent unsupervised Code that starts an AI coding agent with its approval prompts switched off.
Having a capability is not wrongdoing; many tools need these to do their job. It tells you what to check before you install.
This is public metadata, not a safety certification or complete assessment. Static analysis cannot establish what a tool does at runtime.
Risk
Sign in to see this tool's overall risk level and what drives it. Free.
Coverage
Detailed report
3 findings from automated static analysis of the latest version, with severities and explanations.
Using this tool across your team? We can assess your whole inventory.
Request an inventory assessment