Audit loop
npx -y skills add 0SxD/openrouter-swarm-orch-agent --skill audit-loopAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when code has been written or modified. Triggers the 3-agent audit cycle: ZCR (zero-context review) → Semgrep (static analysis) → Opus (cross-reference verdict). Code cannot be committed without passing all three.
SKILL.md
1.5 KB, 316 tokens by cl100k_base, as published. Nobody here has run it
Audit Loop
The triad
- ZCR (Zero-Context Reviewer) — Sonnet agent reads the code cold. No project context, no assumptions about intent. Finds issues a fresh reviewer would find.
- Semgrep (Static Sentinel) — Automated static analysis with auto config. Catches patterns, security issues, code smells mechanically.
- Opus (Orchestrator) — Reviews both ZCR and Semgrep outputs. Cross-references findings. Issues final verdict: PASS, CONDITIONAL (with specific required fixes), or FAIL.
Rules
- ZCR and Semgrep run INDEPENDENTLY — neither sees the other's output
- Opus sees BOTH outputs and makes the final call
- Opus reviews AUDIT RESULTS, not code directly (prevents bias)
- All three must agree for a PASS
- CONDITIONAL means: specific fixes listed, then re-audit
- FAIL means: back to coder with findings (triggers build-loop retry if in a loop)
Commit gate
The audit_gate_check.sh hook blocks git commit without a fresh audit receipt. The receipt must:
- Cover all staged files
- Be less than 1 hour old
- Contain the PASS verdict from the triad
Integration with build-loop
When invoked via /sagex:build-loop, the audit loop is step 2-3 of each round. Failures feed back to the coder for retry. Max 3 rounds before Opus breaks the deadlock.