ck:security

Audit application code for security vulnerabilities using STRIDE and OWASP Top 10.

Updated May 10, 2026
One-click install
npx skills add https://github.com/dthuy62/kollet-app --skill ck-security-dthuy62
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:security
Source: https://github.com/dthuy62/kollet-app/tree/main/.opencode/skills/ck-security
Command: npx skills add https://github.com/dthuy62/kollet-app --skill ck-security-dthuy62

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams identify security weaknesses in application code before release, turning ad hoc review into a structured audit with prioritized findings and practical remediation guidance.

Core Features & Use Cases

  • Structured security auditing: Reviews code through STRIDE and OWASP Top 10 lenses to surface spoofing, tampering, disclosure, and access-control risks.
  • Dependency and secret checks: Adds package vulnerability auditing and hardcoded secret detection to catch common high-impact issues.
  • Optional iterative fixing: Supports fix mode for targeted remediation with guard checks between changes, making it useful for release hardening, auth flows, data-handling features, and compliance prep.

Quick Start

Ask the security skill to audit the target scope and report the highest-risk findings with clear fix recommendations.

Frequently Asked Questions about ck:security

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

FAQPage Schema
How do I audit application code for security vulnerabilities before a release?

To audit application code for security vulnerabilities, this Skill applies STRIDE and OWASP Top 10 analysis to surface spoofing, tampering, and disclosure risks, while checking dependencies and hardcoded secrets to provide prioritized remediation guidance.

What's the best way to find hardcoded secrets and vulnerable dependencies in my codebase?

Finding hardcoded secrets and vulnerable dependencies is handled by this Skill through automated secret pattern detection and package vulnerability auditing, which identifies common high-impact issues alongside standard code review findings.

Can I automatically fix security risks found during an OWASP Top 10 code review?

You can automatically fix security risks found during an OWASP Top 10 code review using the optional iterative fix mode, which applies targeted remediation with guard checks and verification between each change.

Does this security audit tool work on specific file globs or does it require a full repository?

This security audit tool works on both full repositories and scoped file globs, making it suitable for targeted checks during authentication changes, data-handling reviews, and recurring compliance preparation.

How does STRIDE analysis identify access-control risks in my application?

STRIDE analysis identifies access-control risks by reviewing code through structured spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege lenses to surface prioritized security weaknesses.

When should I use an automated code review for compliance checks?

You should use an automated code review for compliance checks during release preparation, authentication changes, and data-handling reviews to structure vulnerability findings and ensure recurring security audits are consistently evaluated.