interrogate
Adversarial pass over a diff or design: three reviewers on different models each try to break it — correctness, security, edge cases — findings merged by severity into a blocking verdict. For contested or high-risk changes.
How do I install this agent skill?
npx skills add https://github.com/yeachan-heo/oh-my-claudecode --skill interrogateIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill facilitates a multi-agent adversarial code review process. It contains a vulnerability to indirect prompt injection and dynamic command execution because the lead agent is instructed to execute shell commands generated by automated "reviewer" agents to verify their findings. If a reviewer model is manipulated by the code it is reviewing, it could produce malicious commands that the lead agent then executes without sanitization.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Interrogate
Three independent reviewers try to break the work before it ships. Diversity
is the mechanism: reviewers on different models or provider families find
different classes of defects, and agreement across them is high-signal. This
is an adversarial lane on top of review, not a replacement for it.
When to use
- a diff or design is contested, high-risk, or security-adjacent
- work is about to ship and a single review pass is not enough evidence
- the user asks to "stress-test", "red-team", or "try to break" a change
When not to use
- routine changes with passing verification —
reviewalone is enough - the deliverable is an answer, not an artifact under judgment
Phase 1 — Frame the target
Name exactly what is under interrogation: the diff (default), a design doc, or an API contract. State the invariants the change must preserve; reviewers attack those first.
Phase 2 — Seat the panel
Spawn three reviewers in one message, in the background, each read-only:
- seat the panel as a diverse-model panel — different provider families
find different defect classes, and agreement across them is high-signal.
Read
team.roleRoutingfrom the project config (.claude/omc.jsonc) or the user config (claude-omc/config.jsonc;omc configprints the effective values) and collect up to three distinct provider families in canonical role order, filling any remaining seats from the default families — claude, codex, gemini — not already seated, and say which family each seat got. When no routing config exists, fall back toOMC_TEAM_WORKTREE_MODE=detached omc team --no-decompose 1:claude,1:codex,1:gemini "<the framed target, the invariants, and one lens per seat>", or in-sessionTaskdispatches tooh-my-claudecode:code-reviewerandoh-my-claudecode:security-revieweron different models — the team command needs the task text; pass target, invariants, and lens allocation as that task - each reviewer gets the same target by path, the invariants, and one lens: correctness, security and trust boundaries, or edge cases and failure modes
- wait for every reviewer to reach a terminal state and collect its output
before Phase 3 — the team route starts workers asynchronously, and
merging before they finish reports an empty panel; a worker that stalls
past the stated interval is named as missing, not silently dropped. Keep
worktrees and team state alive through judging, and run
omc team shutdown <team-name> --force(the name the startup snapshot prints; --force skips the confirmation prompt) only in the final cleanup step after verification, as the arena skill sequences it - instruct each to prove every finding with a run against the real code — a
failing test, a repro script, or command output that shows the wrong
behavior; for a design or plan, a prototype or a probe of the current
tree — and to leave out anything it did not run. No findings is a valid
result. Findings come back as
{severity: blocker|major|minor, claim, evidence, location}where the evidence is the command and the output it printed — a finding without a run is dropped
Phase 3 — Merge
You own the merge. Collect the panels' findings, re-run each finding's command yourself, and keep only what reproduces and breaks the invariants; merge findings that share a root cause, and rank the rest by severity. A claim two reviewers disagree on is a question for the code, not a vote — resolve it by reading or running. In the reply, say how many findings each reviewer produced and how many did not survive the rerun, so a clean panel reads as a result, not a silence.
Phase 4 — Verdict
- block: any blocker finding stands after re-reading the evidence. The work goes back to the author lane with the finding list; nothing merges.
- revise: only major or minor findings. Fix-forward is safe.
- pass: no standing findings. Record the verdict with the reviewers' models named, in the reply.
The verdict is advisory to review and to the human; it never merges or
gates delivery on its own. When interrogation blocks, say what would change
the verdict.
Phase 5 — Cleanup
After the verdict is delivered, run omc team shutdown <team-name> --force (the
name the startup snapshot printed) unconditionally — on pass, revise,
block, and error paths alike. The panel's workers, tmux panes, team state,
and detached worktrees must not outlive the interrogation. Keep the target
checkout intact; only team-managed resources are cleaned.
Rules
- Never count your own review as one of the three.
- A reviewer that cannot run (missing provider, agent limits) is named in the verdict as missing; two reviewers still produce a verdict, one does not.
- Findings are about the artifact, not the author; keep the tone clinical.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/yeachan-heo/oh-my-claudecode/interrogate">View interrogate on skillZs</a>