cso

Audit infrastructure for exposed secrets, dependencies, and LLM threats.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill cso-jia-hong-peng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cso
Source: https://github.com/Jia-Hong-Peng/jolike.com/tree/main/.claude/skills/gstack/cso
Command: npx skills add https://github.com/Jia-Hong-Peng/jolike.com --skill cso-jia-hong-peng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Most security audits only scan application code and miss the real attack surface: exposed secrets in CI logs, stale API keys in git history, vulnerable dependencies, and LLM-specific threats like prompt injection. This Skill provides an infrastructure-first security audit that thinks like an attacker to find the doors that are actually unlocked.

Core Features & Use Cases

  • Infrastructure-First Approach: Audits secrets, dependencies, CI/CD pipelines, and LLM integrations before examining application code, following the principle that most breaches happen outside the app layer.
  • Dual-Mode Scanning: Run zero-noise daily audits with an 8/10 confidence gate to catch only high-certainty issues, or comprehensive monthly deep scans with a 2/10 bar to surface every potential vulnerability.
  • Active Verification & Reporting: Performs active verification of findings and generates Security Posture Reports with severity ratings, confidence scores, and concrete remediation plans without modifying any project files.
  • Use Case: A startup preparing for a compliance audit uses this Skill to identify exposed AWS keys in GitHub history, vulnerable npm dependencies in the supply chain, and missing input validation on webhook endpoints.

Quick Start

Use the cso skill to run a full daily security audit on the current project and review the findings.

Frequently Asked Questions about cso

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a full security audit on my codebase to find exposed secrets and vulnerable dependencies?

To run a full security audit, use this Skill to execute an infrastructure-first scan that uncovers exposed environment variables, stale API keys, and supply chain vulnerabilities. It generates a Security Posture Report with severity ratings and remediation plans without modifying project code.

Can I use this audit to find LLM-specific security threats like prompt injection?

Yes, you can use this audit to find LLM-specific security threats like prompt injection. The Skill performs infrastructure-first security audits that specifically include LLM integrations and skill supply chain analysis in its comprehensive security posture assessment.

What is the best way to identify stale API keys and exposed environment variables in my CI/CD pipelines?

The best way to identify stale API keys and exposed environment variables is using an infrastructure-first security audit. This approach examines CI/CD pipelines and git history before application code, actively verifying findings to generate actionable Security Posture Reports.

Does this security audit modify my project files during the OWASP Top 10 scan?

No, this security audit does not modify your project files during the OWASP Top 10 scan. It performs active verification of findings and generates Security Posture Reports with concrete remediation plans while keeping your project code completely untouched.