cso

Audit infrastructure security across secrets, dependencies, CI/CD, and LLM/AI systems.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/sanskarbasnet/fstack --skill cso-sanskarbasnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cso
Source: https://github.com/sanskarbasnet/fstack/tree/main/cso
Command: npx skills add https://github.com/sanskarbasnet/fstack --skill cso-sanskarbasnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security audits of modern infrastructure are complex, time-consuming, and error-prone. The CSO mode in fstack provides an infrastructure-first security audit encompassing secrets archaeology, dependency supply chain, CI/CD pipeline security, LLM/AI security, and skill-supply-chain scanning to raise security posture with repeatable processes.

Core Features & Use Cases

  • Secrets archaeology: detect exposed credentials and sensitive data across repos and environments.
  • Dependency supply chain scanning: identify vulnerable transitive dependencies and unsafe packages.
  • CI/CD pipeline security: enforce secure pipelines and guard against misconfigurations.
  • LLM/AI security and prompt hygiene: verify data handling, prompt safety, and model interactions.
  • Skill supply chain scanning: validate that included skills and integrations come from trusted sources.
  • OWASP Top 10 and STRIDE threat modeling: structured risk assessment with active verification.
  • Modes: daily zero-noise checks and comprehensive monthly deep scans; trend tracking across runs.

Quick Start

Run a CSO audit on your current project by activating the cso skill to perform a daily security check, and schedule a monthly comprehensive pass.

Frequently Asked Questions about cso

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

FAQPage Schema
How do I audit infrastructure security across CI/CD pipelines and dependencies?

Infrastructure security audits require scanning CI/CD pipelines, dependency supply chains, and secrets archaeology. This skill performs end-to-end checks using OWASP Top 10 and STRIDE threat modeling to identify exposed credentials, unsafe packages, and pipeline misconfigurations across your build lifecycle.

What is secrets archaeology and how does it find exposed credentials?

Secrets archaeology detects exposed credentials and sensitive data across repositories and environments. By scanning historical commits and configuration files, it identifies hardcoded secrets and unauthorized data access points to secure your infrastructure against credential leaks.

Can I use STRIDE threat modeling to assess my deployment lifecycle?

STRIDE threat modeling structures risk assessment across your build and deployment lifecycle. This skill applies STRIDE alongside OWASP Top 10 methodologies to actively verify security posture, categorize threats, and validate data handling within your infrastructure.

Does the audit support both daily security checks and monthly deep scans?

Daily security checks and monthly deep scans are supported through two operating modes. Daily checks enforce a zero-noise confidence gate at 8/10 for routine passes, while monthly deep scans lower the threshold to 2/10 for comprehensive vulnerability discovery and trend tracking.

How do I scan LLM and AI security for prompt hygiene vulnerabilities?

LLM and AI security scanning verifies prompt hygiene, data handling, and model interactions. This skill audits your AI integrations to detect prompt injection risks, validate data safety protocols, and ensure secure model interactions within your infrastructure.

Do I need Claude Code environment tooling to run supply chain security scans?

Claude Code environment tooling and fstack routines are required to activate and run supply chain security scans. The skill leverages frontmatter metadata to drive activation, using these integrations to validate that included dependencies and skills come from trusted sources.