cso

Scan code, infrastructure, and dependencies for security risks and secrets.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/fghaffar/faystack --skill cso-fghaffar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cso
Source: https://github.com/fghaffar/faystack/tree/main/cso
Command: npx skills add https://github.com/fghaffar/faystack --skill cso-fghaffar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizations need to identify hidden security risks, leaked credentials, supply‑chain vulnerabilities, and misconfigurations before attackers exploit them.

Core Features & Use Cases

  • Comprehensive scanning across code, infrastructure, CI/CD pipelines, and dependencies.
  • Secret archaeology to find exposed keys in git history and env files.
  • Supply‑chain and OWASP checks for vulnerable packages and common web flaws.
  • Two modes: daily quick audit with an 8/10 confidence gate, or a deep monthly scan with a 2/10 gate.
  • Report generation delivering findings, severity ratings, and remediation steps.

Quick Start

Ask the assistant to run /cso for a complete security posture report of the current repository.

Frequently Asked Questions about cso

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

FAQPage Schema
How do I scan for exposed secrets and leaked credentials in git history?

To scan for exposed secrets in git history, you can run a security audit that performs secret archaeology across code, git history, and env files. This process identifies exposed keys and delivers findings with severity ratings and remediation steps.

What is the best way to audit CI/CD pipelines and dependencies for supply-chain vulnerabilities?

Auditing CI/CD pipelines and dependencies for supply-chain vulnerabilities requires a comprehensive security scan across infrastructure and project files. The audit identifies misconfigurations and vulnerable packages, generating a structured security posture report.

Can I run a quick daily security audit instead of a full monthly scan?

You can run a quick daily security audit using a mode with an 8/10 confidence gate, designed for rapid checks. Alternatively, a deep monthly scan operates with a 2/10 confidence gate to find subtle risks across the repository.

Does the security audit check for OWASP issues and web application flaws?

The security audit includes OWASP checks to identify common web application flaws alongside vulnerable packages. It scans code and infrastructure to detect these issues, providing severity ratings and actionable remediation steps in the final report.

What do I need to access before running a full security posture report on my repository?

Running a full security posture report requires repository access and Git history to scan effectively. The audit utilizes Bash, Grep, and Claude tools, along with optional web search capabilities, to analyze code, infrastructure, and dependencies.