ck:security

Detect and categorize security vulnerabilities across web application codebases.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/hidonguyen/trade-ops --skill ck-security-hidonguyen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:security
Source: https://github.com/hidonguyen/trade-ops/tree/main/.opencode/skills/ck-security
Command: npx skills add https://github.com/hidonguyen/trade-ops --skill ck-security-hidonguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates a structured security audit to find, categorize, and prioritize vulnerabilities across a codebase, reducing manual review time and surfacing critical risks before release.

Core Features & Use Cases

  • STRIDE + OWASP analysis: Systematically evaluates spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege while mapping findings to OWASP Top 10 categories.
  • Secret detection & dependency audit: Scans for hardcoded secrets using regex patterns and runs dependency vulnerability checks appropriate to the detected stack.
  • Iterative safe fixes: Optionally applies prioritized fixes with guard checks and commits, using an iterative approach that stops on regression.
  • Use Case: Run a pre-release audit on a web application to identify critical secrets and injection risks, generate a severity-ranked report, and optionally apply safe automated remediations.

Quick Start

Run ck:security on the src/ directory to produce a severity-ranked findings report and optionally apply iterative fixes with --fix and --iterations.

Frequently Asked Questions about ck:security

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

FAQPage Schema
How do I find and fix security vulnerabilities in my web application codebase?

To find and fix security vulnerabilities, you can run an automated audit that scans source files, configurations, and dependencies for OWASP Top 10 issues and hardcoded secrets, producing a severity-ranked report with optional iterative auto-fixes.

What is STRIDE analysis and how does it map to OWASP Top 10 checks?

STRIDE analysis systematically evaluates spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege risks, mapping discovered vulnerabilities directly to OWASP Top 10 categories for structured triage and remediation.

How do I scan source code for hardcoded secrets and dependency vulnerabilities?

Scanning for hardcoded secrets and dependency vulnerabilities involves using regex pattern matching to detect exposed credentials and running stack-appropriate dependency audits to identify at-risk packages, outputting structured findings for remediation.

Can I automatically apply security fixes to my codebase without breaking existing functionality?

You can automatically apply security fixes using an iterative approach that applies prioritized remediations, runs guard checks, and commits changes, stopping safely if a regression is detected to protect existing functionality.

What is the best way to run a pre-release security audit on a web application?

Running a pre-release security audit involves scanning the project directory to identify critical secrets and injection risks, generating a severity-ranked findings report, and optionally applying safe automated remediations before release.

Does this security audit target specific file types or the entire project directory?

The security audit targets the entire project directory by scanning source files, configuration files, and dependencies to ensure comprehensive coverage of web application vulnerabilities and hardcoded secrets.