Menu

Individual skill

security

0upvotes

Review the security of a change, a release, or a feature the way a team has to answer for it: the assets and trust boundaries in scope, the project's own scanners run, threats walked per boundary, every finding verified against the code with the path from entry point to impact, a checklist from the client or the company answered item by item with evidence, and the residual risk left for a named person to accept. Also keeps the threat model of a feature current. Use before a release that touches authentication, personal data, payments, or an external integration, when a client asks for a security checklist, or when a design needs its threats written down before anyone builds it. Triggers on: "security review", "security audit", "security checklist", "threat model", "STRIDE", "OWASP", "kiểm tra bảo mật", "đánh giá bảo mật", "checklist bảo mật", "mô hình mối đe dọa", "セキュリティレビュー", "セキュリティチェックリスト", "脅威モデル", "脆弱性診断", "is this secure enough to ship", "/atk:security".

plugins/atk/skills/security/SKILL.md

Read pinned source

Source commit 55481d2e4ae3cec8e2050c160303c751bbf20173

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
12
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Security Review (`atk:security`)

Produces the security record a Tech Lead can sign and a client can read: what was in scope, what was
checked and how, what was found with the evidence behind it, and what is left open with the name of
whoever accepted it. A finding without a path from an entry point to an impact is a worry, not a
finding, and the record keeps the two apart.

## Scope

Handles: resolving the scope into assets, actors, entry points, and trust boundaries; running the
project's own dependency audit and the secret scan over tracked files; walking the threats per
boundary against `references/threat-checklist.md`; verifying each candidate against the code;
answering a supplied security checklist item by item; and writing or updating the threat model of a
feature.