gstack-cso

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

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill gstack-cso-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-cso
Source: https://github.com/adamtpang/summon.company/tree/main/.claude/skills/gstack-cso
Command: npx skills add https://github.com/adamtpang/summon.company --skill gstack-cso-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security reviews of a codebase are slow, inconsistent, and often miss infrastructure-level risks like leaked secrets in git history, unsafe CI/CD workflows, or LLM-specific attack vectors. This Skill runs a structured, multi-phase security audit that covers both application code and the surrounding infrastructure, with confidence-gated reporting to reduce noise. ## Core Features & Use Cases - Infrastructure-first audit phases: secrets archaeology in git history, dependency supply chain analysis, CI/CD pipeline security, Docker/IaC review, webhook signature verification, LLM/AI security checks, and skill supply chain scanning. - 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. - OWASP Top 10, STRIDE threat modeling, and data classification: systematic coverage of access control, injection, SSRF, and per-component threat evaluation. - Use Case: Before a release, ask for a security audit of your repository; the Skill detects your stack, scans for leaked credentials and vulnerable dependencies, reviews GitHub Actions workflows, and produces a severity-ranked report with false-positive filtering. ## Quick Start Ask the agent to run a security audit of this repository and report only high-confidence vulnerabilities with severity ratings.

Frequently Asked Questions about gstack-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 Claude Code?

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

What does the daily vs comprehensive audit mode difference mean?

Daily mode reports only findings with 8/10 confidence or higher to eliminate noise during regular development. Comprehensive mode lowers the bar to 2/10 for monthly deep scans, surfacing lower-confidence issues for manual review.

Can this detect 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 whether .env files are tracked, and flags CI configs with inline credentials.

Does the audit cover LLM and AI-specific vulnerabilities?

Yes. Phase 7 checks for prompt injection vectors, unsanitized LLM output rendered as HTML, unvalidated tool calling, hardcoded AI API keys, and eval of LLM-generated content.

Why does the audit skip some security tools during a run?

Package manager audit tools are optional. If a tool like npm audit is not installed, the skill notes it as skipped with install instructions and continues with whatever tools are available rather than failing.

What are the limitations of static security scanning?

The audit uses code tracing only and never makes live requests to endpoints, so it cannot confirm exploitability dynamically. Findings require human verification, and active penetration testing needs a separate live-testing tool.