security

Audit codebases for OWASP Top 10 and STRIDE threats with evidence-backed reports.

204|14|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/garagon/nanostack --skill security-garagon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/garagon/nanostack/tree/main/security
Command: npx skills add https://github.com/garagon/nanostack --skill security-garagon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Many releases fail because critical vulnerabilities, leaked secrets, or insecure CI/dependency configurations are missed until after deployment. This Skill systematically uncovers OWASP Top 10 issues, secret exposures in code and history, and architectural threats so teams can remediate before shipping.

Core Features & Use Cases

  • OWASP & STRIDE Audits: Full OWASP A01–A10 coverage and per-component STRIDE threat modeling with prioritized findings.
  • Secrets & Dependency Scans: Git history checks, secrets redaction, and dependency vulnerability audits with actionable upgrade advice.
  • CI/CD and Infrastructure Checks: Detect unpinned GitHub Actions, exposed secrets in workflows, Docker misconfigs, and AI endpoint risks.
  • Use Case: Run this Skill on a pre-release branch or PR to produce an evidence-backed report listing file locations, exploitation scenarios, and precise code fixes.

Quick Start

Use the security skill to run an OWASP Top 10 and STRIDE audit over the repository and produce an actionable report.

Frequently Asked Questions about security

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

FAQPage Schema
How do I run an OWASP Top 10 security audit on my codebase before a release?

To run an OWASP Top 10 security audit, execute this Skill against your pre-release branch or pull request to systematically uncover vulnerabilities and generate an evidence-backed report with file locations, exploitation steps, and code fixes.

Can I detect hardcoded secrets and exposed credentials in my Git history?

Yes, you can detect hardcoded secrets by running a secrets scan that checks your code and Git history for exposed credentials, redacts them, and provides actionable advice to secure your repository before shipping.

What is STRIDE threat modeling and how does it apply to component-level security reviews?

STRIDE threat modeling is a structured approach to identifying architectural threats, and this Skill applies it per component to systematically discover security risks across web, backend, and library repositories during pre-ship checks.

Does this security audit check for insecure CI/CD configurations and Docker misconfigurations?

Yes, this security audit reviews CI/CD workflows and Docker configurations to detect unpinned GitHub Actions, exposed secrets in workflows, Docker misconfigs, and AI endpoint risks to prevent insecure deployments.

How do I scan dependencies for known vulnerabilities in my web or backend repository?

You can scan dependencies for known vulnerabilities by running this Skill against your repository manifests to perform dependency vulnerability audits and receive actionable upgrade advice for at-risk packages.

What is the best way to find and fix insecure dependency configurations before deployment?

The best way to find and fix insecure dependency configurations is to run this Skill on a pre-release branch to audit manifests, identify vulnerabilities, and produce a report detailing precise code fixes and remediation steps.