cso

Audit repositories, CI/CD pipelines, and dependency supply chains for security issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects the real security risks a repository exposes beyond unit tests and quick scans: leaked secrets, CI/CD misconfigurations, dependency supply chain issues, insecure infrastructure, and unsafe AI/skill integrations. It turns noisy checklists into prioritized, actionable findings so teams can fix what attackers actually exploit.

Core Features & Use Cases

  • Attack surface mapping: inventory endpoints, workflows, IaC, containers, and external integrations to show what an attacker can reach.
  • Secrets archaeology & git history scanning: find leaked keys, tracked .env files, and dangerous commits with high-confidence rules.
  • Dependency and supply chain analysis: surface vulnerable or malicious packages, missing lockfiles, and install-time scripts in production deps.
  • CI/CD and infra checks: detect unpinned actions, pull_request_target risks, privileged containers, and overly permissive IAM.
  • AI/skill supply chain and LLM security: scan skills for prompt-injection patterns, permission misuse, and provenance issues.
  • Report generation: produce a Security Posture Report with severity, confidence, and remediation plans; supports daily (low-noise) and comprehensive (deep) modes.

Quick Start

Run the cso skill to perform a daily infrastructure-first audit of the current repository and generate a prioritized Security Posture Report.

Frequently Asked Questions about cso

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

FAQPage Schema
How do I perform a security audit of my CI/CD pipelines and dependency supply chain?

A repository security audit detects leaked secrets in git history, CI/CD misconfigurations, vulnerable dependencies, and unsafe AI skill integrations. It maps the attack surface by inventorying endpoints, workflows, IaC, and external integrations to identify what attackers can actually exploit.

What is LLM security and how does it apply to AI skill integrations?

Secrets archaeology scans git history to find leaked keys, tracked .env files, and dangerous commits using high-confidence rules. This process exposes hardcoded credentials and sensitive environment configurations that attackers could exploit if left unresolved in the repository.

Does this security audit support diff scans and Grep-based code searches?

This security audit detects unpinned GitHub Actions, pull_request_target risks, privileged containers, and overly permissive IAM roles. By performing these CI/CD and infrastructure checks, it identifies pipeline misconfigurations that could allow unauthorized access or malicious code execution.

What is the difference between daily and comprehensive audit modes for repository security?

Dependency and supply chain analysis surfaces vulnerable or malicious packages, missing lockfiles, and risky install-time scripts in production dependencies. This audit identifies compromised external libraries that could introduce vulnerabilities or unauthorized code execution paths into your repository infrastructure.