Skills Prompts

Popular categories

Agent skill · gstack

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

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.

Works with

  • Claude Code
  • Codex, Cursor, OpenCode, Gemini CLI and other agents

Used forSecurity audits

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. 1
    Resolve scope

    Flags choose infrastructure, code, supply chain, skills, OWASP or a named domain, optionally limited to the branch diff.

  2. 2
    Model the application

    The agent maps stacks, actors, assets, tenant boundaries and sensitive operations, then lists every entry point in scope.

  3. 3
    Audit and challenge

    Selected phases run, and each candidate is checked by an independent reviewer for attacker control, impact and existing protections.

  4. 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. 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.

Install this skill

It installs with the gstack pack.

Claude CodeThe README wraps this command in a prompt you paste into Claude Code, which also adds a short gstack section to CLAUDE.md.
git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup
Claude Code (team mode for a shared repo)Run inside your repo; it commits a bootstrap so teammates get gstack with auto-updates, and needs Node.js for the required hook.
(cd ~/.claude/skills/gstack && ./setup --team) && ~/.claude/skills/gstack/bin/gstack-team-init required && git add .claude/ CLAUDE.md && git commit -m "require gstack for AI-assisted work"
Codex, Cursor, OpenCode, Gemini CLI and other agentsUse --host auto for every detected agent or name one host; non-Claude hosts are listed as experimental.
git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/gstack
cd ~/gstack && ./setup --host auto # or: ./setup --host codex
./setup --status # one row per install: host, tier, scope, version, path

Commands come from the author’s README; check it for changes before you run them.

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.

More guides from gstack

Also in this pack

All 30 skills →

Summary by trendhub. The skill itself lives in garrytan/gstack/cso by Garry Tan (MIT); read the full, current text there.