security-engineer

Audits application code for OWASP Top 10 vulnerabilities, auth flaws, and data exposure.

176|49|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/nagisanzenin/production-grade --skill security-engineer-nagisanzenin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-engineer
Source: https://github.com/nagisanzenin/production-grade/tree/main/skills/security-engineer
Command: npx skills add https://github.com/nagisanzenin/production-grade --skill security-engineer-nagisanzenin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping code without a structured security review leaves applications exposed to injection attacks, broken access control, auth bypasses, and compliance gaps. This Skill performs a systematic, multi-phase application security audit that produces concrete findings with file-and-line references and executable fixes. ## Core Features & Use Cases - STRIDE Threat Modeling: Maps attack surfaces, trust boundaries, and data flow threats per service with risk-scored threat matrices. - OWASP Top 10 Code Audit: Reviews every endpoint and code path for injection, broken access control, cryptographic failures, and SSRF, with each finding tied to a specific file and line. - Auth, Data & Supply Chain Review: Traces authentication flows, audits token management and RBAC policies, inventories PII across databases, logs, and caches, and evaluates dependencies with contextual severity re-evaluation. - Remediation Plan & Pen Test Suite: Delivers prioritized fixes with before/after code, verification tests, an API fuzzing configuration, and per-service attack scenarios. - Use Case: After implementing and testing a multi-service web application, run this Skill in the hardening phase to receive a full security audit report, critical vulnerability fixes with code, and a recurring audit schedule before launch. ## Quick Start Ask the agent to run a full security audit of the services and frontend code, covering threat modeling, OWASP review, auth flows, data security, and dependencies, and produce a prioritized remediation plan.

Frequently Asked Questions about security-engineer

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?▼

Run this Skill after implementation and testing are complete. It audits all ten OWASP categories against your actual code, and every finding includes the vulnerable file and line, a proof-of-concept explanation, and a specific remediation with fixed code.

What does a STRIDE threat model include for web services?▼

The threat model produces a per-service STRIDE table covering spoofing, tampering, repudiation, information disclosure, denial of service, and privilege escalation. It also maps the attack surface, trust boundaries, and data flow threats with likelihood-impact risk scores.

Does this cover infrastructure security like WAF rules and IAM policies?▼

No. This Skill handles application-level security only: code vulnerabilities, auth logic, data handling, and dependencies. Infrastructure concerns such as WAF configuration, IAM policies, network security groups, and container image scanning belong to the DevOps skill.

Can it audit authentication flows and RBAC policies?▼

Yes. Phase 3 traces registration, login, password reset, OAuth2/OIDC, and MFA flows through the actual middleware code, catalogs every token type, and reviews RBAC policies for horizontal and vertical privilege escalation across all endpoints.

When should a security audit run in the development lifecycle?▼

It runs in the hardening phase, after implementation and testing are complete. Auditing unstable code wastes effort because findings become stale as the codebase changes. The remediation plan also defines recurring audits for dependency updates and architecture changes.

How are dependency vulnerability severities evaluated?▼

Scanner CVSS scores are re-evaluated in context rather than accepted blindly. The audit checks whether the vulnerable code path is reachable and whether the input is user-controlled, then adjusts severity with documented justification.