cso

Audits codebases for secrets, dependency, CI/CD, and OWASP vulnerabilities with severity-rated reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security reviews often miss the real attack surface: leaked credentials in git history, vulnerable dependencies, misconfigured CI/CD pipelines, and exposed infrastructure. This Skill runs a structured, multi-phase security audit that produces a concrete Security Posture Report with severity ratings and remediation plans, without making any code changes. ## Core Features & Use Cases - Secrets Archaeology: Scans git history, tracked .env files, and CI configs for leaked credentials like AWS keys, GitHub tokens, and Slack tokens. - Supply Chain & Pipeline Security: Audits dependencies for CVEs and install scripts, and checks CI/CD workflows for unpinned actions, pull_request_target abuse, and script injection. - OWASP & Threat Modeling: Covers OWASP Top 10, STRIDE threat modeling, and infrastructure shadow surface analysis (Dockerfiles, IaC, config files with prod credentials). - Use Case: Before a release, run a full daily audit with an 8/10 confidence gate to catch high-signal issues, or run a monthly comprehensive deep scan with a 2/10 bar to surface lower-confidence findings across the entire repository. ## Quick Start Ask the assistant to run a security audit of this repository using the cso skill and report the findings with severity ratings.

Frequently Asked Questions about cso

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

FAQPage Schema
How do I run a security audit on my repository?

Invoke the skill with no flags for a full daily audit covering all phases with an 8/10 confidence gate. Use the comprehensive flag for a monthly deep scan with a lower 2/10 bar that surfaces more potential findings.

How to find leaked secrets in git history?

The secrets archaeology phase scans git history for known credential patterns like AKIA, sk-, ghp_, and xoxb- tokens, checks for tracked .env files, and flags CI configs with inline secrets. Active secrets in history are rated CRITICAL.

Can I audit only dependencies or only CI/CD pipelines?

Yes, scope flags limit the audit to specific areas: supply-chain for dependency audits, infra for infrastructure phases, code for application code, owasp for OWASP Top 10, and skills for skill supply chain. Scope flags are mutually exclusive.

Does the security audit make code changes automatically?

No, the skill never modifies code. It produces a Security Posture Report containing concrete findings, severity ratings from CRITICAL to MEDIUM, and remediation plans that the user reviews and acts on.

What happens if WebSearch is unavailable during the audit?

Checks requiring WebSearch are skipped and the report notes that it proceeded with local-only analysis. All other phases, including secrets scanning and dependency audits, continue normally.