cso

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

1|Updated Jul 23, 2026
One-click install
npx skills add https://github.com/sanjanb/my-agent-harness --skill cso-sanjanb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cso
Source: https://github.com/sanjanb/my-agent-harness/tree/main/skills/cso
Command: npx skills add https://github.com/sanjanb/my-agent-harness --skill cso-sanjanb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security reviews are often skipped or shallow because manual audits are slow and noisy. This Skill runs a structured, infrastructure-first security audit of a repository with confidence-gated reporting so only high-signal findings surface. ## Core Features & Use Cases - Multi-phase audit coverage: secrets archaeology in git history, dependency supply chain analysis, CI/CD pipeline security, webhook signature verification, LLM/AI security checks, 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 runs. - Use Case: Before shipping a release, run a security audit to catch a leaked API key in git history, an unpinned GitHub Action, and a webhook endpoint missing signature verification, then receive a severity-ranked report with false-positive filtering. ## Quick Start Ask the agent to run a security audit on this repository and report only high-confidence vulnerabilities.

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 with an AI agent?

Invoke the skill with a phrase like "security audit" or "OWASP review". It auto-detects your stack, then runs phased checks covering secrets, dependencies, CI/CD, webhooks, and LLM security, producing a severity-ranked report.

What does the daily vs comprehensive audit mode difference mean?

Daily mode applies an 8/10 confidence gate so only high-certainty findings are reported, keeping noise near zero. Comprehensive mode is a monthly deep scan with a 2/10 reporting bar that surfaces lower-confidence leads for manual review.

Can it find leaked secrets in git history?

Yes. Phase 2 runs secrets archaeology using git log searches for known credential prefixes like AKIA, ghp_, sk-, and xoxb-, checks tracked .env files, and flags CI configs with inline credentials instead of secret stores.

Does the audit check GitHub Actions and CI/CD pipeline security?

Yes. Phase 4 inspects workflow files for unpinned third-party actions, dangerous pull_request_target triggers, script injection via github.event interpolation in run steps, and secrets exposed as environment variables.

Does it cover LLM and AI-specific vulnerabilities like prompt injection?

Yes. Phase 7 greps for user input flowing into system prompts, unsanitized LLM output rendered as HTML, eval of AI responses, hardcoded AI API keys, and unvalidated tool or function calling.

Why might a reported finding be a false positive?

Each phase ships explicit false-positive rules: placeholders and test fixtures are excluded, devDependency CVEs cap at MEDIUM, and user content in normal chat messages is not flagged as prompt injection. Findings require traced evidence before reporting.