agentic-security:security-scan-on-deploy

Automate security scans before production deploys and surface top findings.

73|15|Updated May 6, 2026
One-click install
npx skills add https://github.com/Clear-Capabilities/agentic-security --skill agentic-security-security-scan-on-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-security:security-scan-on-deploy
Source: https://github.com/Clear-Capabilities/agentic-security/tree/main/skills/security-scan-on-deploy
Command: npx skills add https://github.com/Clear-Capabilities/agentic-security --skill agentic-security-security-scan-on-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Activates before deployment to help determine if a project is safe to ship by warning about destructive deploy commands and potential risks.

Core Features & Use Cases

  • Early risk verdict: detects when a deploy may be unsafe and surfaces critical findings to prevent accidental release.
  • Guided remediation: suggests path for triage and fix flow to make deploys safer.
  • Production-aware checks: optionally respects filters and blocks risky deploys when configured.

Quick Start

Ask the agent to run a security scan before deploying to production.

Frequently Asked Questions about agentic-security:security-scan-on-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a security scan before deploying to production?

A pre-deploy security scan prevents unsafe releases by reading last-scan.json state and surfacing top findings by exploitability. It applies to ship, deploy, and launch workflows, warning about destructive commands and potential risks before production deployment.

How does pre-deploy security triage work for CI pipelines?

Pre-deploy security triage for CI pipelines reads last-scan.json state and surfaces top findings by exploitability. It applies to ship and launch workflows, guiding remediation with optional filters and gating rules to block risky deploys when configured.

Can I block risky production deploys using automated security gating rules?

Yes, you can block risky production deploys by configuring optional gating rules. The scan respects configured filters, detects unsafe deploy commands, and blocks risky deploys to prevent accidental release of vulnerable code.

What is the best way to assess deployment risks before a manual launch?

The best way to assess deployment risks before a manual launch is to trigger an early risk verdict scan. It detects unsafe deploy commands, surfaces critical findings by exploitability, and suggests a path for guided remediation.

Does the pre-deploy security scan work with manual deploy workflows?

Yes, the pre-deploy security scan works with manual deploy workflows and CI pipelines. It activates before deployment to determine if a project is safe to ship, including prompts to run a scan before manual releases.