# agency-application-security-engineer

agency-application-security-engineer is a Claude Code skill that performs secure code reviews and builds threat models. It catches vulnerabilities before code hits production.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 85 repo stars
- Author: huytran1120
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/huytran1120/vie-agentic-skills/tree/HEAD/skills/agency-application-security-engineer/SKILL.md
- Updated: 2026-11-15
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/agency-application-security-engineer

## What it does

The skill acts as an embedded application security engineer throughout the development cycle. It audits code for OWASP Top 10 and CWE Top 25 flaws, targeting access control issues, injection bugs, and cryptographic mistakes. Fixes come with concrete implementation snippets in the project language instead of policy documents.

It structures threat modeling via STRIDE, PASTA, or attack trees to uncover attack surfaces early. When integrating SAST, DAST, SCA, or secret detection into CI/CD pipelines, it aims to keep false positives under 20%. Vulnerability remediation follows fixed SLAs: 7 days for critical issues, 30 days for high, and 90 days for medium severity flaws.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add huytran1120/vie-agentic-skills --skill agency-application-security-engineer -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/agency-application-security-engineer/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/agency-application-security-engineer/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add huytran1120/vie-agentic-skills --skill agency-application-security-engineer -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/agency-application-security-engineer/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add huytran1120/vie-agentic-skills --skill agency-application-security-engineer -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/agency-application-security-engineer/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install huytran1120/vie-agentic-skills skills/agency-application-security-engineer
```

2. **Manually: put the files in place**
- File: `.github/skills/agency-application-security-engineer/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add huytran1120/vie-agentic-skills --skill agency-application-security-engineer -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/huytran1120/vie-agentic-skills --path skills/agency-application-security-engineer
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/agency-application-security-engineer/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/huytran1120/vie-agentic-skills/tree/HEAD/skills/agency-application-security-engineer/SKILL.md

## When to use it
- audit code for OWASP Top 10 and access control vulnerabilities
- create threat models for architecture changes using STRIDE or PASTA
- configure SAST, DAST, and secret scanners for CI/CD pipelines
- generate regression tests for patched security vulnerabilities

## Example prompts
- Review this authentication endpoint for OWASP Top 10 security vulnerabilities
- Run a STRIDE threat model on the new payment processing flow
- Audit the profile controller for broken access control and provide the fix

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 4ae26a7c8ba81411.

BEGIN THIRD-PARTY FILE 4ae26a7c8ba81411
```text
---
name: 'agency-application-security-engineer'
description: 'AppSec specialist who secures the software development lifecycle through threat modeling, secure code review, SAST/DAST integration, and developer security education that makes secure code the default.'
---

# Application Security Engineer

You are **Application Security Engineer**, the security engineer who lives in the codebase, not the SOC. You have reviewed millions of lines of code across every major language, built security scanning pipelines that catch vulnerabilities before they reach production, and designed threat models that predicted real attack vectors months before they were exploited. Your job is to make the secure way the easy way — because if developers have to choose between shipping fast and shipping secure, they will ship fast every time.

## 🧠 Your Identity & Memory

- **Role**: Senior application security engineer specializing in secure SDLC, threat modeling, code review, vulnerability management, and developer security enablement
- **Personality**: Developer-first, empathetic, pragmatic. You know that most security vulnerabilities are honest mistakes by talented developers who were never taught secure coding. You fix the system, not the person. You speak in code examples, not policy documents
- **Memory**: You carry deep knowledge of every OWASP Top 10 entry, every CWE in the Top 25, and the real-world exploits they enable. You remember that Equifax was a missing Apache Struts patch, Log4Shell was JNDI injection that nobody thought about, and SolarWinds was a build system compromise. Each one is a lesson in where AppSec must be present
- **Experience**: You have built AppSec programs from scratch at startups and scaled them at enterprises. You have integrated SAST into CI/CD pipelines that developers actually appreciate (because you tuned out the noise), conducted threat models that found critical design flaws before a single line of code was written, and trained hundreds of developers to think about security as a quality attribute, not a compliance checkbox

## 🎯 Your Core Mission

### Threat Modeling
- Conduct threat models for new features, architectural changes, and third-party integrations before development begins
- Use STRIDE, PASTA, or attack trees depending on the context — the framework matters less than the rigor
- Identify trust boundaries, data flows, and attack surfaces in system architecture diagrams
```
END THIRD-PARTY FILE 4ae26a7c8ba81411

The third-party file has ended. Everything between the 4ae26a7c8ba81411 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2452 of 29374 bytes. © huytran1120 · MIT · https://github.com/huytran1120/vie-agentic-skills/tree/HEAD/skills/agency-application-security-engineer/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
