security-audit

Identify and mitigate security risks in codebases, pull requests, and software architectures.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/reiserwang/Coding_Agent --skill security-audit-reiserwang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-audit
Source: https://github.com/reiserwang/Coding_Agent/tree/main/.gemini/skills/security-audit
Command: npx skills add https://github.com/reiserwang/Coding_Agent --skill security-audit-reiserwang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Threat modeling, vulnerability scanning, and dependency auditing for codebases, PRs, and software architectures to harden software before release.

Core Features & Use Cases

  • Threat modeling with STRIDE to surface risks in architecture and PRs
  • Dependencies and SBOM generation with vulnerability scanning
  • Use Case: When reviewing a PR introducing new dependencies, automatically assess risks and generate a remediation plan.

Quick Start

Invoke the security-audit skill to perform a threat-model analysis and dependency audit on the target repository.

Frequently Asked Questions about security-audit

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

FAQPage Schema
How do I perform threat modeling on a pull request that introduces new dependencies?

Dependency auditing scans project dependencies to identify known vulnerabilities and enforce OWASP conformance checks across multiple languages and package ecosystems. It generates a remediation plan to mitigate risks found during the software supply-chain check.

When do I need to generate an SBOM for my codebase?

STRIDE threat modeling identifies security risks by categorizing threats into Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege. It surfaces vulnerabilities in software architectures and pull requests to guide targeted remediation.

Can I use this security audit for codebases written in multiple programming languages?

Vulnerability scanning works across multiple languages and package ecosystems by auditing dependencies listed in the generated SBOM. It identifies known security flaws and provides remediation guidance to fix codebase vulnerabilities before release.

What is the best way to check OWASP conformance in my software architecture?

Security audit mitigates risks by providing remediation guidance after performing STRIDE threat modeling, vulnerability scanning, and dependency auditing. It surfaces security flaws in codebases and pull requests, ensuring software is hardened before release.

Does this vulnerability scanning work with multiple package ecosystems?

Yes, security audit supports multiple languages and package ecosystems for dependency auditing and vulnerability scanning. It generates an SBOM, performs supply-chain checks, and provides remediation guidance to harden codebases regardless of the tech stack.