← All use cases

Run a deep security scan

Dig through an authorized repository for plausible vulnerabilities.

Try the Security plugin's Deep Security Scan skill for a more exhaustive repository audit, and know its limits in ZeroTwo before you rely on it.

Advanced
Long-running

Skills & Plugins

  • Security: Deep Security Scan
    The Security plugin skill that repeats repository-wide discovery over several rounds, validates the merged candidates once, then reports. Pick it from the $ menu.

Starter prompt

Use the Deep Security Scan skill from the Security plugin on this repository; I own it and have approval to audit it. Use the build notes in AGENTS.md as scan guidance. When it finishes, tell me where the scan output is saved, summarize which findings were validated and which were not, and list the areas that weren't covered. Don't change any code.

Choose a deep repository review

Try this when you want the most exhaustive repository-wide pass and a longer run is acceptable. The skill is for a whole repository, not a single folder, pull request or diff. For changes and diffs use the plugin's Security Diff Scan skill, described in Scan code changes for security.

Prepare an authorized scan

Install the Security plugin from Customize > Plugins and confirm you are authorized to audit the code. Put build commands and security-relevant notes in AGENTS.md, which the scan uses as repository-specific guidance, then run the prompt. If the skill reports that it cannot run its parallel discovery, accept that result rather than a reduced run, and start an ordinary Security scan instead. When it does run, the scan saves a Markdown report and an HTML report in its own scan folder; read both and note the proof gaps.

Review evidence before remediation

Check reachability, validation and remaining gaps, separating unvalidated from validated findings. Fix only reviewed ones, via Remediate a vulnerability backlog.

Related use cases