Rust Security Review Runs in the main conversation (invoke via ). Orchestrator owns the ledger as bookkeeping for retries; workers and judges have no Task tools. Workers and judges are named plugin subagents ( , , ); tool sets are declared in . Findings are exchanged via markdown-with-YAML files in a shared output directory. When to Use Rust application/library security review: safe/unsafe boundary auditing, memory safety in blocks, concurrency hazards, panic-induced DoS on servers, FFI safety, async-runtime mistakes. When NOT to Use - Pure-C / pure-C++ codebases — use instead. - Smart contra…