security-audit

Identify and mitigate security flaws in pre-merge code reviews.

15|5|Updated May 17, 2026
One-click install
npx skills add https://github.com/cropsgg/skills --skill security-audit-cropsgg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/cropsgg/skills/tree/main/skills/engineering/security-audit
Command: npx skills add https://github.com/cropsgg/skills --skill security-audit-cropsgg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps security-minded teams review code changes to identify weak trust boundaries, insecure defaults, and gaps in authentication and authorization before merging, reducing risk in production deployments.

Core Features & Use Cases

  • Define and validate trust models across components and data flows during code changes.
  • Inventory sensitive surfaces, insecure defaults, and access controls; propose mitigations and verification steps.
  • Use cases include pre-merge reviews of authentication/authorization changes, input handling, and third-party integration risks.

Quick Start

Review a code change and generate a remediation plan addressing trust boundaries, authentication, and insecure defaults.

Frequently Asked Questions about security-audit

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

FAQPage Schema
How do I audit trust boundaries and authentication logic in a pre-merge code review?

Pre-merge security audit of trust boundaries requires explicit trust modeling across components and data flows to identify insecure defaults and access control gaps before merging. You inventory sensitive surfaces and validate authentication changes to reduce production deployment risk.

What is threat modeling during code review and when do I need it?

Threat modeling during code review defines and validates trust models across components and data flows to identify weak trust boundaries before deployment. You need it when reviewing authentication, authorization, session handling, secrets, and input handling changes.

How do I review authorization and session handling changes for security flaws?

Reviewing authorization and session handling changes requires inventorying sensitive surfaces and access controls to identify insecure defaults and gaps. You propose mitigations with documented verification steps and reproducible evidence to ensure secure third-party integrations.

Does this security audit approach work for third-party integration risks and config changes?

Security audit applies to pre-merge reviews of code, config, and third-party integrations to identify access control gaps and insecure defaults. It validates trust models across data flows and generates remediation plans addressing authentication and authorization risks.

What is the best way to document mitigations for insecure defaults found during a security audit?

Documenting mitigations for insecure defaults requires proposing verification steps with reproducible evidence during the security audit. You inventory sensitive surfaces, validate trust models, and generate a remediation plan addressing weak trust boundaries and authentication gaps.