aegis-protocol

Review changed code for exploitable security vulnerabilities with CVSS v4.0 scoring.

12|3|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/Fei2-Labs/skill-genie --skill aegis-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aegis-protocol
Source: https://github.com/Fei2-Labs/skill-genie/tree/main/skills/aegis-protocol
Command: npx skills add https://github.com/Fei2-Labs/skill-genie --skill aegis-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a high-confidence code security review workflow for changed code, ensuring security-sensitive areas are protected before merging PRs.

Core Features & Use Cases

  • Threat-Informed Analysis: Uses modern methodologies like NIST CSF, MITRE ATT&CK, OWASP, and SLSA for security reviews.
  • False-Positive Filtering: Reports only exploitable findings, focusing on changed code.
  • CVSS v4.0 Scoring: Assigns severity scores for prioritization.
  • Supply-Chain Verification: Includes SLSA supply-chain verification for secure dependencies.
  • Use Case: Before merging a PR, use this Skill to perform a structured security audit of recent diffs to ensure there are no security vulnerabilities.

Quick Start

Run Aegis Protocol on the current branch vs origin/HEAD to perform a security review.

Frequently Asked Questions about aegis-protocol

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

FAQPage Schema
How do I perform a threat-informed code review on recent git diffs?

To perform a threat-informed code review on recent git diffs, you need a Git and Python environment to analyze changed code against frameworks like MITRE ATT&CK and OWASP, filtering out false positives to ensure only exploitable findings are reported.

Can I use CVSS v4.0 scoring to prioritize security vulnerabilities before merging a PR?

Yes, you can use CVSS v4.0 scoring to prioritize security vulnerabilities before merging a PR by running a structured security audit on your current branch versus origin/HEAD to assign severity scores to exploitable findings.

Does this code security review verify software supply-chain dependencies?

Yes, this code security review verifies software supply-chain dependencies by applying SLSA supply-chain verification alongside OWASP and NIST CSF methodologies to ensure security-sensitive areas are protected before merging.

What is the best way to reduce false positives in automated code security reviews?

The best way to reduce false positives in automated code security reviews is to focus threat-informed analysis strictly on changed code, prioritizing exploitability so that only high-confidence, genuinely exploitable findings are reported.

Do I need Python and Git to run SLSA supply-chain verification on code changes?

Yes, you need Python and Git installed to run SLSA supply-chain verification on code changes, as the review process relies on a Python environment with necessary libraries to analyze git diffs and score vulnerabilities.

Why does my code security review only scan the changed code instead of the whole repository?

Your code security review only scans the changed code instead of the whole repository to prioritize exploitability and perform high-confidence threat-informed analysis, ensuring security-sensitive areas are efficiently protected before a PR merge.