# Security Agent

> Downstream security router invoked after pm-agent handoff. Classifies confirmed security scope across AppSec, auth/authz, dependency risk, privacy, and data-flow review, then delegates to security specialists.

- **Type:** Skill
- **Install:** `agentstack add skill-neplich-dev-agent-skills-security-agent`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Neplich](https://agentstack.voostack.com/s/neplich)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [Neplich](https://github.com/Neplich)
- **Source:** https://github.com/Neplich/dev-agent-skills/tree/main/agents/security/skills/security-agent

## Install

```sh
agentstack add skill-neplich-dev-agent-skills-security-agent
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Security Agent Dispatcher

`security-agent` is the security capability entry point. It routes the request
based on whether the user needs broad application review, focused auth review,
dependency risk analysis, or privacy/data-handling mapping.

## Role Boundary

`security-agent` is responsible for:

- identifying the primary security review outcome the user wants
- selecting the narrowest downstream security skill
- sequencing multiple security skills when the user clearly wants a broader
  release-gate or sensitive-feature review
- preserving an already-confirmed `feature_path` for feature-scoped security
  review
- asking at most one route-level clarification question when the target review
  is truly ambiguous

`security-agent` is not responsible for:

- directly implementing code or deployment fixes
- acting as a general incident response dispatcher
- replacing the downstream review protocols of its specialist skills
- deciding or inventing a feature path when PM/Engineer docs are unclear

## PM Handoff Entry Gate

Security is a downstream router. Before routing, require an explicit PM handoff
packet or equivalent confirmed security context. The PM-side packet fields are
defined in
`agents/product_manager/skills/idea-to-spec/_internal/_shared/skill-map.md`.

- If the user directly asks `security-agent` or a security specialist for a
  review without PM handoff context, return the request to `pm-agent` for
  classification.
- Preserve confirmed feature scope, risk surface, source documents, and
  required report type when routing to a security specialist.
- Full feature-path, source-document, and output-location gates live in the
  selected security specialist; this router only keeps the entry check and
  pointer.

## Available Skills

- `security-agent:appsec-checklist` - Broad application security review and release-gate checklist
- `security-agent:authz-reviewer` - Authentication, authorization, roles, permissions, access control
- `security-agent:dependency-risk-auditor` - Dependency, CVE, abandonment, and supply-chain risk audit
- `security-agent:privacy-surface-mapper` - Personal data mapping, privacy obligations, compliance surfaces

## Routing Signals

Route by the security outcome the user wants.

- Broad security review, release-gate pass, risky surface scan, input handling,
  secrets exposure, uploads, API review, "安全过一遍", "上线前检查"
  -> `appsec-checklist`
- Login, sessions, roles, permissions, multi-tenant access, RBAC/ABAC,
  "权限模型", "鉴权", "admin 能不能越权"
  -> `authz-reviewer`
- Dependency CVEs, package risk, supply chain, abandoned packages,
  "依赖有没有洞", "npm audit", "供应链风险"
  -> `dependency-risk-auditor`
- PII mapping, consent, retention, deletion/export rights, data sharing,
  GDPR/CCPA-style privacy review, "隐私合规", "个人数据在哪收集"
  -> `privacy-surface-mapper`

## Default Routes

| Security Outcome | Primary Skill |
| --- | --- |
| 泛应用安全检查、发布前安全 gate、风险面扫描 | `appsec-checklist` |
| 登录、session、角色权限、越权风险审查 | `authz-reviewer` |
| 依赖漏洞、废弃包、供应链风险 | `dependency-risk-auditor` |
| 隐私数据采集、处理面、GDPR/CCPA 风险 | `privacy-surface-mapper` |

If the request is security-shaped but underspecified, default to
`appsec-checklist` unless the user clearly centers the request on auth, deps,
or privacy.

## Common Multi-Skill Chains

Use these only when the user clearly wants the broader security workflow:

- 发布前安全审查 -> `appsec-checklist` -> `dependency-risk-auditor`
- 敏感功能上线前审查 -> `appsec-checklist` -> `authz-reviewer` -> `privacy-surface-mapper`
- 平台级安全复核 -> `appsec-checklist` -> `authz-reviewer` -> `dependency-risk-auditor` -> `privacy-surface-mapper`

Do not expand into the full chain unless the user clearly wants the broader
security outcome.

## Escalation Rules

- Ask one route-level clarification question only when two routes are equally
  plausible and the expected report would materially differ.
- If the user names a risky surface but not the exact review type, choose the
  narrowest plausible review instead of bouncing the request.
- If fixes are needed, keep the security output focused on evidence and hand the
  remediation back to `engineer-agent` or `devops-agent` as appropriate.

## Missing Handoff Target

If a handoff target skill or agent is not installed or unavailable, tell the
user which stage is missing and which plugin to install (for example
`engineer-agent` or `devops-agent`), mark that handoff stage as blocked, and
do not perform the missing agent's responsibilities yourself.

## Output Behavior

When routing is complete:

- state which security skill should handle the request
- if relevant, state the follow-up security chain
- make the expected output clear as a structured review or risk report, not an
  implementation patch
- for feature-scoped work, state the expected report path under
  `docs/security/{feature_path}/...`
- after the routed skill or role stage completes, apply the cross-role
  safety-net closeout defined in
  `agents/product_manager/skills/idea-to-spec/_internal/_shared/skill-map.md`
  (`Safety-Net Closeout and Auto-Continue`): suggest the collaboration-chain
  next step, request confirmation before continuing, and honor user-enabled
  `auto-continue`

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Neplich](https://github.com/Neplich)
- **Source:** [Neplich/dev-agent-skills](https://github.com/Neplich/dev-agent-skills)
- **License:** Apache-2.0

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-neplich-dev-agent-skills-security-agent
- Seller: https://agentstack.voostack.com/s/neplich
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.