cso

Audit code, CI/CD, dependencies, and cloud infrastructure for exposed secrets and supply-chain threats.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many codebases and pipelines expose secrets, risky CI/CD workflows, vulnerable dependencies, or misconfigured infrastructure that attackers can exploit; manual audits are slow and noisy. cso provides a focused, confidence-gated audit workflow that finds high-signal issues across git history, dependencies, CI, and infrastructure so teams can fix the real doors that are open.

Core Features & Use Cases

  • Stack & architecture detection: build a mental model from README/CLAUDE.md and config files to prioritize searches.
  • Secrets archaeology: scan git history, tracked .env files, and CI configs for exposed credentials and leaked tokens.
  • Dependency & supply-chain analysis: detect missing lockfiles, install scripts in production deps, and known CVEs.
  • CI/CD and IaC checks: analyze GitHub Actions, workflows, Dockerfiles, Terraform and Kubernetes manifests for dangerous patterns.
  • Modes & scopes: run daily zero-noise audits, comprehensive deep scans, or scoped checks (infra, code, skills, supply-chain) and diff-only branch analysis.
  • Reporting: produce a Security Posture Report with prioritized findings, severity ratings, and remediation steps.

Quick Start

Run the cso skill to perform an infrastructure-first security audit and generate a Security Posture Report with prioritized findings and remediation steps.

Frequently Asked Questions about cso

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

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

You can perform a security audit on repositories and branches using daily zero-noise audits, comprehensive monthly deep scans, scoped inspections (infra, code, skills, supply-chain), and diff-limited branch checks. This confidence-gated workflow finds high-signal issues across git history, dependencies, CI, and infrastructure.

How does CI/CD and IaC analysis detect risky workflows?

Dependency and supply-chain analysis detects missing lockfiles, install scripts in production dependencies, and known CVEs. By checking dependency lockfiles and install scripts, the audit identifies vulnerable components and supply-chain threats within your codebase.

Can I run a security audit scoped to just infrastructure or supply-chain?

The audit produces a Security Posture Report with prioritized findings, severity ratings, and remediation steps. This confidence-gated reporting ensures teams receive zero-noise results during daily audits and comprehensive details during monthly deep scans.

What is the best way to detect vulnerable dependencies and supply-chain threats?

The confidence-gated reporting workflow uses daily zero-noise audits and comprehensive monthly deep scans to filter out false positives. This approach ensures you only receive prioritized findings with severity ratings and remediation steps for actual exposed secrets and risky workflows.