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
- 1Resolve scope
Flags choose infrastructure, code, supply chain, skills, OWASP or a named domain, optionally limited to the branch diff.
- 2Model the application
The agent maps stacks, actors, assets, tenant boundaries and sensitive operations, then lists every entry point in scope.
- 3Audit and challenge
Selected phases run, and each candidate is checked by an independent reviewer for attacker control, impact and existing protections.
- 4Reproduce 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.
- 5Report 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 && ./setupClaude 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, pathCommands 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
/office-hoursPressure-test an idea before your agent writes any codeQuestions your idea in startup or builder mode, challenges premises, compares two or three approaches and writes a design doc, with no code.Read the guide →/plan-ceo-reviewReview a plan for scope and ambition like a founderReviews a plan as a founder would, in expansion, selective, hold or reduction mode, and asks before adding or cutting any scope.Read the guide →/plan-eng-reviewLock architecture, edge cases and tests before you buildLocks a plan's architecture, data flow, edge cases and test coverage, with ASCII diagrams and a review report appended to the plan.Read the guide →/qaFind, reproduce and fix bugs with regression testsTests a site, API, CLI, job or webhook, reproduces each bug, writes a regression test first and commits each verified fix.Read the guide →/reviewCatch production bugs in a diff before it mergesReviews a branch diff for bugs that pass CI, dispatches specialist and adversarial passes, auto-fixes obvious issues and asks about the rest.Read the guide →/shipTake a branch from finished code to an open PRMerges the base branch, runs tests and reviews, bumps VERSION and CHANGELOG, verifies the frozen content, pushes and opens a PR.Read the guide →
Also in this pack
/autoplanRuns the CEO, design, developer experience and engineering reviews in sequence and brings only taste decisions to you.↗/benchmarkMeasures page load timings, Core Web Vitals and resource sizes in a real browser and compares them with a saved baseline.↗/browseDrives a real browser, preferring your signed-in Aside sessions, to open pages, click through flows, read the console and take screenshots.↗/canaryWatches a live URL after a deploy for console errors, failed pages and visual changes against baseline screenshots.↗/codexGets an independent review, challenge or consultation from the OpenAI Codex CLI and presents its output unedited.↗/design-consultationResearches your product space and proposes a full design system, written to a DESIGN.md file with font and colour previews.↗/design-htmlTurns an approved mockup into production HTML and CSS with computed text layout, detecting React, Svelte or Vue.↗/design-reviewAudits a live site for spacing, hierarchy and generated-looking patterns, then fixes them with atomic commits and before and after screenshots.↗/design-shotgunProduces several AI design mockups side by side in a browser board, collects your feedback and iterates until you pick a direction.↗/devex-reviewTests a developer product live by following its docs and getting-started flow, timing each step and comparing against the plan's scores.↗/diagramTurns an English description into a mermaid source, an editable Excalidraw file and rendered SVG and PNG, offline.↗/document-releaseChecks project docs against what changed in a release and updates the facts, asking about subjective edits.↗
Summary by trendhub. The skill itself lives in garrytan/gstack/cso by Garry Tan (MIT); read the full, current text there.