ck:security

Audit codebases with STRIDE and OWASP to identify and rank vulnerabilities.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill performs a structured security audit using STRIDE and OWASP frameworks to identify and rank vulnerabilities, delivering a prioritized findings report.

Core Features & Use Cases

  • Structured STRIDE analysis across codebases and configurations
  • OWASP Top 10 mapping, dependency and secret detection, and remediation guidance
  • Iterative fix support via ck:autoresearch-style guard patterns to prevent regressions

Quick Start

Audit the target scope with the ck:security command to generate a structured findings report.

Frequently Asked Questions about ck:security

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

FAQPage Schema
How do I automate a STRIDE security audit for my codebase?

Automate a STRIDE security audit by running a structured analysis across your codebase and configurations to identify, map, and rank vulnerabilities. It applies to pre-release reviews, post-auth feature changes, and periodic repository checks.

Can I map identified vulnerabilities to the OWASP Top 10 during an audit?

OWASP Top 10 mapping is supported natively during the audit. The process identifies vulnerabilities through STRIDE analysis and directly maps them to OWASP categories, running dependency and secret detection alongside structured reporting.

What is the best way to perform a security check on scoped file sets before release?

Security checks on scoped file sets are handled by defining a target scope for the audit. It performs structured STRIDE analysis and OWASP mapping on the specified files, generating a prioritized findings report for pre-release reviews.

Does the audit process support iterative fixes to prevent security regressions?

Iterative fix support is included to prevent regressions during remediation. It applies guard patterns after identifying vulnerabilities, ensuring that applied fixes do not introduce new security issues into the codebase.

When do I need a structured STRIDE analysis for my repository?

Structured STRIDE analysis is needed for periodic security checks on full repositories, pre-release reviews, or post-auth and data-handling feature changes. It identifies and ranks vulnerabilities to deliver a prioritized findings report.