security-review

Perform risk-tiered security analysis with STRIDE and CWE/CVSS mappings.

9|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/TykoDev/SupremeTeam --skill security-review-tykodev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/TykoDev/SupremeTeam/tree/main/skills/review/security-review
Command: npx skills add https://github.com/TykoDev/SupremeTeam --skill security-review-tykodev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill finds exploitable security defects, compliance gaps, and supply-chain risks in shipped code so reviewers can prioritize remediation and validate security requirements before release.

Core Features & Use Cases

  • Risk-tiered analysis: Classify changes as Low/Medium/High and adapt review depth accordingly.
  • Framework-aligned findings: Map findings to NIST SSDF, OWASP ASVS, OWASP Top 10, and CWE Top 25 for consistent classification and compliance evidence.
  • Threat modeling integration: Use STRIDE and ATT&CK cross-references to validate mitigations for trust-boundary and data-flow changes.
  • Supply-chain evaluation: Enforce SBOM generation, SCA with reachability analysis, provenance (SLSA) checks, and secrets detection on dependency changes.
  • AI-specific checks: Detect prompt injection, data/model poisoning risks, excessive agent privileges, and PII leakage in AI components.
  • Deliverable output: Produce a structured Security Review Report with CWE/CVSS mappings and a machine-readable pipeline summary for automated gates.

Quick Start

Run the security-review skill on the target repository or pull request to produce a risk-tiered Security Review Report and machine-readable pipeline summary.

Frequently Asked Questions about security-review

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

FAQPage Schema
How do I perform a security review on a pull request to identify exploitable vulnerabilities?▼

A security review on a pull request applies STRIDE threat modeling and risk-tiered analysis to identify exploitable vulnerabilities. It outputs a structured Security Review Report with CWE mappings and CVSS v4.0 severity ratings for remediation.

What is STRIDE threat modeling and how does it validate security mitigations?▼

STRIDE threat modeling identifies security risks across trust boundaries and data flows to validate mitigations. It cross-references ATT&CK techniques to ensure shipped code changes are properly secured against exploitable vulnerabilities.

How do I map security findings to NIST SSDF and OWASP ASVS compliance frameworks?▼

Security findings are mapped to NIST SSDF and OWASP ASVS by classifying vulnerabilities against their compliance requirements during risk-tiered code analysis. This framework-aligned approach ensures consistent classification and generates actionable compliance evidence.

Can I use automated security gates to verify supply-chain risks and SBOM generation?▼

Automated security gates verify supply-chain risks by enforcing SBOM generation, SCA reachability analysis, and SLSA provenance checks on dependency changes. The review outputs a machine-readable pipeline summary to validate these requirements before release.

Does security analysis detect prompt injection and data poisoning risks in AI components?▼

Security analysis detects AI-specific risks including prompt injection, data and model poisoning, excessive agent privileges, and PII leakage. These checks are integrated into the risk-tiered review to secure AI components before deployment.

What is the best way to assess CVSS v4.0 severity for identified code vulnerabilities?▼

Assessing CVSS v4.0 severity is best achieved through a structured security review that evaluates exploitable vulnerabilities in shipped code. The process generates a report detailing severity scores and supply chain status for prioritized remediation.