cso

Audits codebases for secrets, supply chain risks, CI/CD flaws, and OWASP vulnerabilities.

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

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 LLM-specific threats. This Skill runs a structured, multi-phase security audit that produces a prioritized Security Posture Report instead of ad-hoc checklist scanning. ## Core Features & Use Cases - Infrastructure-first auditing: Scans git history for leaked secrets, checks dependency supply chains, reviews CI/CD pipeline security, and maps shadow infrastructure like Dockerfiles and IaC configs. - Code-level analysis: Covers OWASP Top 10, STRIDE threat modeling, LLM/AI security checks (prompt injection, RAG poisoning), and skill supply chain scanning. - Two confidence modes: Daily mode reports only high-confidence findings (8/10 gate) for zero-noise reviews; comprehensive mode (2/10 bar) surfaces everything for monthly deep scans, with trend tracking across runs. - Use Case: Before a release, run /cso --diff to audit only the changes on your branch, or run /cso --comprehensive monthly to catch stale API keys, unpinned GitHub Actions, and vulnerable dependencies across the whole repo. ## Quick Start Ask the AI to run a full security audit of the current repository and produce a prioritized security posture report with severity ratings 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 run a security audit on my codebase with AI?

Invoke the /cso command with no flags to run all audit phases in daily mode, which reports only high-confidence findings. Use /cso --comprehensive for a monthly deep scan that surfaces lower-confidence issues across the entire repository.

What does a supply chain security audit check beyond npm audit?

It checks for install scripts in production dependencies, lockfile existence and git tracking, abandoned packages, and known CVEs in direct dependencies. Standard package manager audit tools run when available, with skipped tools noted in the report.

Can I audit only the changes on my current branch?

Yes, the --diff flag constrains every phase to files and configs changed on the current branch versus the base branch. It combines with any scope flag and with --comprehensive mode.

Does the audit cover LLM and AI-specific security risks?

Yes, a dedicated phase checks for prompt injection, RAG poisoning, and tool calling permission issues in AI-enabled applications. A separate phase scans the skill supply chain for malicious or flawed AI agent skills.

What CI/CD security issues does the audit detect?

It detects unpinned third-party GitHub Actions, dangerous pull_request_target triggers, script injection via github.event context in run steps, secrets exposed as environment variables, and missing CODEOWNERS protection on workflow files.

Why does the daily audit miss some vulnerabilities?

Daily mode applies an 8/10 confidence gate that intentionally suppresses lower-confidence findings to eliminate noise. Run comprehensive mode with its 2/10 bar when you need full coverage and can triage more results.