cso

Audits repositories for secrets, supply chain, CI/CD, LLM, and OWASP vulnerabilities.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aicodepro/ai-agent-nexi --skill cso-aicodepro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cso
Source: https://github.com/aicodepro/ai-agent-nexi/tree/main/agent/skills/gstack/cso
Command: npx skills add https://github.com/aicodepro/ai-agent-nexi --skill cso-aicodepro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security reviews are often shallow checklist scans that miss leaked credentials in git history, vulnerable dependencies, misconfigured CI/CD pipelines, and AI-specific attack vectors like prompt injection. This Skill runs a structured, multi-phase security audit of a repository with confidence-gated reporting so teams get actionable findings instead of noise. ## Core Features & Use Cases - Multi-phase audit coverage: Secrets archaeology in git history, dependency supply chain analysis, CI/CD pipeline security, infrastructure shadow surface, webhook signature verification, LLM/AI security, skill supply chain scanning, OWASP Top 10, STRIDE threat modeling, and data classification. - Two audit modes: A daily zero-noise mode with an 8/10 confidence gate and a comprehensive monthly deep scan with a 2/10 reporting bar, plus trend tracking across audit runs. - Use Case: Before shipping a release, invoke the audit to scan git history for leaked API keys, check GitHub Actions for unpinned actions and pull_request_target risks, and verify webhook endpoints enforce signature verification. ## Quick Start Ask the assistant to run a security audit on this repository and report only high-confidence findings.

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 a phrase like "security audit" or "CSO review". It runs stack detection first, then executes the audit phases matching your selected mode, and reports only findings that pass the confidence gate.

What is the difference between daily and comprehensive audit modes?

Daily mode reports only findings at 8/10 confidence or higher for zero-noise signal. Comprehensive mode is a monthly deep scan with a 2/10 reporting bar, covering all phases including OWASP Top 10 and STRIDE threat modeling.

Can this detect leaked secrets in git history?

Yes. Phase 2 performs secrets archaeology by searching git history for known credential prefixes like AKIA, ghp_, sk-, and xoxb-, checks for tracked .env files, and flags CI configs with inline secrets instead of secret stores.

Does the audit cover LLM and AI-specific vulnerabilities?

Yes. Phase 7 checks for prompt injection vectors, unsanitized LLM output rendered as HTML, tool calling without validation, hardcoded AI API keys, and eval of LLM output, with severity ratings and false-positive rules.

Does the security audit make live requests to webhook endpoints?

No. Webhook verification is code-tracing only. The audit traces handler code and middleware chains to confirm signature verification exists, and never sends actual HTTP requests to endpoints.