security

Run automated SAST and SCA scans on changed code and dependencies.

86|21|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/davidmatousek/tachi --skill security-davidmatousek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/davidmatousek/tachi/tree/main/.claude/skills/security
Command: npx skills add https://github.com/davidmatousek/tachi --skill security-davidmatousek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude-powered SAST and SCA security scan skill. Invoked automatically as the Security Scan step (Step 7) of /aod.build (after Design Quality Gate, before Code Simplification) or standalone via /security. Analyzes all code files and dependency manifests changed on the feature branch relative to main for OWASP Top 10 vulnerability patterns and known CVE findings. Produces a human-readable security-scan.md report and machine-readable .security/ compliance artifacts (scan-log.jsonl, vulnerabilities.jsonl, SARIF 2.1.0, CycloneDX 1.5 SBOM). Blocks build progression on CRITICAL/HIGH findings with an explicit acknowledgment gate. Use --no-security in /aod.build to skip. Invoke /security directly for standalone analysis outside the build pipeline.

Core Features & Use Cases

  • SAST and SCA: detect OWASP Top 10 patterns and CVEs in changed code and manifests
  • Artifact generation: produces human-readable reports and machine-readable artifacts
  • Governance gate: blocks build on CRITICAL/HIGH findings and supports explicit acknowledgment
  • Flexible invocation: usable within /aod.build security step or standalone /security scans

Quick Start

Run /security in any project directory to perform an automated security scan and generate audit artifacts.

Frequently Asked Questions about security

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

FAQPage Schema
How do I automate SAST and SCA security scans for code changes in CI-CD?

Automate SAST and SCA security scans by running /security in any project directory to detect OWASP Top 10 patterns and known CVEs in changed code and dependency manifests. The scan generates human-readable reports and machine-readable compliance artifacts like SARIF and CycloneDX SBOM.

What is the best way to block CI-CD pipeline builds on critical vulnerabilities?

Block CI-CD pipeline builds on critical vulnerabilities by enforcing a governance gate that stops progression on CRITICAL or HIGH findings. The security scan requires explicit acknowledgment before allowing the build to continue, ensuring unmitigated high-severity risks are reviewed.

How does SAST vulnerability scanning work for feature branch changes?

SAST vulnerability scanning for feature branches works by analyzing all changed code files relative to the main branch. It identifies OWASP Top 10 vulnerability patterns in the modified code and outputs both human-readable security reports and machine-readable JSON logs for governance.

Can I generate SARIF and CycloneDX SBOM artifacts for compliance auditing?

You can generate SARIF 2.1.0 and CycloneDX 1.5 SBOM artifacts for compliance auditing by running an automated SCA scan on dependency manifests. The scan produces these machine-readable compliance artifacts alongside a human-readable security-scan.md report.

Does the security scan require any specific dependencies or components to run?

The security scan does not require any specific dependencies or external components to run. It operates standalone within any project directory using the /security command, or automatically as a built-in step within the /aod.build pipeline.

Why is my security scan blocking the build pipeline progression?

Your security scan is blocking build pipeline progression because it detected CRITICAL or HIGH severity vulnerabilities in your changed code or dependencies. The governance gate enforces this block and requires explicit acknowledgment of the findings before the build can proceed.