# /cso: Run a security audit that keeps evidence separate from claims

Source: https://trendhub.net/skills/garrytan-gstack/cso
Skill folder: https://github.com/garrytan/gstack/tree/main/cso
Pack: gstack (https://trendhub.net/skills/garrytan-gstack)
Works with: Claude Code, Claude Code (team mode for a shared repo), Codex, Cursor, OpenCode, Gemini CLI and other agents

The CSO skill audits a repository through a trusted helper rather than reading source directly. It maps actors, assets and entry points, censuses the attack surface, runs scope-specific phases and has each candidate independently challenged. Reports state whether coverage is complete, partial or not assessed, and comprehensive mode can reproduce a finding and test repair candidates in Docker without changing your branch.

## When to use it

- You want a security pass over a codebase before a launch or audit.
- A branch touches authentication, uploads or webhooks and needs a diff-scoped review.
- You want a suspected vulnerability reproduced and a fix tested in isolation.

## How it works

1. **Resolve scope**: Flags choose infrastructure, code, supply chain, skills, OWASP or a named domain, optionally limited to the branch diff.
2. **Model the application**: The agent maps stacks, actors, assets, tenant boundaries and sensitive operations, then lists every entry point in scope.
3. **Audit and challenge**: Selected phases run, and each candidate is checked by an independent reviewer for attacker control, impact and existing protections.
4. **Reproduce when possible**: In comprehensive mode a matching runtime profile lets it show the bug fails, test a patch on a clean copy and run the full suite.
5. **Report coverage**: The report opens with complete, partial or not assessed, then lists findings with severity, confidence, evidence and repair advice.

## What it steers the agent away from

- Treating scanner output or repo instructions as trusted.
- Printing environment variables or secrets while checking prerequisites.
- Calling a finding fixed without new evidence on current source.

## What it can touch

Runs gstack's CSO launcher, which snapshots and reads the repo, can run scanners and Docker containers, and stores redacted reports in gstack's state folder.

## Pairs well with

- `/careful`
- `/review`

## Questions

### Do I need Docker?

Only for comprehensive runtime reproduction. Without Docker or a matching profile it still runs a static assessment.

### Which stacks support reproduction?

Node, Bun, Python and Rails, and only when a qualified runtime profile matches the project.
