Source instructions onlyA profile for using Claude Code to run broad security checks without treating the output as gospel.

Install or setup path

Install gstack from the upstream repository, then enable the documented security-audit workflow and adapt its checks to your own trust boundaries and deployment surface.

No verified install command on this page

This profile is useful for evaluation and workflow context, but WhichAITools did not verify one direct install command for it. Use the linked source instructions instead of guessing.

Use this profile for

Teams that need a repeatable first-pass security workflow during code review, release prep, or repository onboarding.

Primary categorySecurity Review
Source count3
OpenClaw relevantNo

What it does

This profile frames the security-audit workflow around Claude Code: scanning for OWASP-style app risks, obvious secret exposure, insecure defaults, dependency red flags, and trust-boundary mistakes that deserve a deeper manual review.

Best for

Teams that need a repeatable first-pass security workflow during code review, release prep, or repository onboarding.

Why it stands out

Security work benefits from breadth first. A strong audit skill helps sweep the obvious risk surface quickly so humans can spend their limited time validating the findings that matter.

Adopt this skill carefully

Return to the parent path

Move back to the category or hub instead of jumping to the homepage and losing context.

Cross-check the method

Review methodology and manuals before treating a public profile or copied command like production-ready guidance.

Use the surrounding workflow hub

When the profile belongs to OpenClaw operations, continue inside the OpenClaw cluster instead of starting over.

Safety notes

  • Audit output requires human validation before remediation or sign-off because Claude Code can miss context, overstate issues, or invent risk where none exists.
  • Treat secret scanning and dependency findings as the start of investigation, not final proof of exposure.
  • Verify trust boundaries manually when the repository touches auth, payments, user data, or infrastructure control planes.

Source context

This profile is grounded in the public gstack cso skill, which explicitly frames security work around secrets, supply chain, OWASP, and threat modeling. Anthropic's best-practices guide adds first-party guidance around verification, permissions, and tool usage, which matters when turning a security checklist into an executable Claude Code workflow.

gstack cso skillgstack GitHub repositoryBest Practices for Claude Code

Related profiles

AI Code Review Skill

Use this profile when the main goal is diff analysis: spotting regressions, missing tests, risky assumptions, or release-boundary mistakes before a change merges.

Skill Safety Review

Use this profile when a team needs a repeatable way to screen public skills for hidden assumptions, risky permissions, or maintenance gaps.

MCP Server Setup

Use this profile when Claude Code needs live access to databases, APIs, file systems, or operator tools through MCP and you want the connection model to stay legible.