Plugin

audit-project

Multi-agent iterative code review until zero issues remain. Spawns up to 10 specialist reviewers (code quality, security, performance, test coverage, architecture, database, API, frontend, backend, DevOps) chosen based on the project's signals. Each pass produces certainty-graded findings (HIGH / MEDIUM / LOW); HIGH findings auto-fix where safe. The orchestrator iterates passes until zero open issues remain or a max-iteration cap is reached. Specialists are role-based (defined inline via Task tool, not file-based agents) so they don't bloat the plugin's agent count. Designed to plug into /next-task and /prepare-delivery as the deep-review phase.

• Published source
• Repository

Analysed

11 October 2026

Last observed

14 October 2026

About this tool

What does this mean?

Listing details come from the registries and repositories where the tool is published. They help you judge who maintains it and how active it is; they are not a safety signal.

Listed on

Claude Plugin Marketplaces

Tracked by Verune

since 10 October 2026 · 1 version observed

What the code does

What does this mean?

These are capabilities our static analysis found in the latest published version. They describe what the code can do, not whether it is malicious: many tools need shell access or the network to do their job. Use them to decide what to check before installing.

• 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.

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.