cso

Audit infrastructure, dependencies, and CI/CD pipelines to produce a security posture report.

43|7|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/lucas-flatwhite/gstack-ko --skill cso-lucas-flatwhite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cso
Source: https://github.com/lucas-flatwhite/gstack-ko/tree/main/cso
Command: npx skills add https://github.com/lucas-flatwhite/gstack-ko --skill cso-lucas-flatwhite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security teams struggle to gain a cohesive view of an organization's risk posture across infrastructure, dependencies, and CI/CD pipelines. This Skill provides a centralized Security Posture Report with prioritized remediation guidance for leadership and engineering teams.

Core Features & Use Cases

  • Infrastructure-first security audit: secrets archaeology, pipeline security, threat modeling, and active verification.
  • Dependency supply chain analysis: identify vulnerable or tampered dependencies and suggest mitigations.
  • LLM/AI security checks: guardrails for prompt handling, tool usage, and output safety in AI-assisted workflows.
  • OWASP Top 10 & STRIDE threat modeling: structured risk assessment across systems and data flows.
  • Modes: daily quick checks for near-term risk and comprehensive monthly scans for deeper coverage.

Quick Start

Run the daily audit with /cso for an 8/10 confidence gate, or /cso --comprehensive for a monthly deep scan.

Frequently Asked Questions about cso

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

FAQPage Schema
How do I conduct a security posture audit for infrastructure and CI/CD pipelines?

Security posture auditing evaluates infrastructure, dependencies, and CI/CD pipelines to produce a formal report. It targets daily risk assessments and monthly deep reviews covering secrets archaeology and supply chain analysis.

What is secrets archaeology and supply chain analysis in infrastructure security?

Secrets archaeology uncovers hidden credentials in infrastructure, while supply chain analysis identifies vulnerable or tampered dependencies. Both are core mechanisms for generating actionable remediation plans in a security posture report.

Can I use this Skill for LLM security and AI workflow guardrails?

Yes, this Skill includes LLM security checks that evaluate guardrails for prompt handling, tool usage, and output safety. It assesses ML/AI security considerations specifically within AI-assisted workflows.

Do I need upstream gstack tooling and threat-modeling capabilities to run an audit?

Yes, generating actionable remediation plans requires upstream gstack tooling and threat-modeling capabilities. These prerequisites support structured risk assessment using OWASP Top 10 and STRIDE methodologies.

What is the best way to monitor daily risk versus performing a monthly deep scan?

The best approach is running daily quick checks for near-term risk with an 8/10 confidence gate, and comprehensive monthly scans for deeper coverage. This dual-mode strategy ensures continuous security posture visibility.

When should I not use an automated security posture report for threat modeling?

Automated security posture reports require upstream gstack tooling and are designed for structured OWASP Top 10 and STRIDE assessments. They are not suitable for environments lacking CI/CD pipelines or dependency tracking infrastructure.