Retroactively verify threat mitigations for a completed phase
Scanned 9/11/2026
Install to Claude Code
npx -y skills add buildomator/buildomator --skill secure-phase --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Secure Phase?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/buildomator-secure-phase-buildomator)More formats (shields.io, HTML) on the badges page.
---
name: secure-phase
description: Retroactively verify threat mitigations for a completed phase
argument-hint: "[phase number]"
allowed-tools:
- Read
- Write
- Edit
- Bash
- Glob
- Grep
- Task
- AskUserQuestion
---
<objective>
Verify threat mitigations for a completed phase. Three states:
- (A) SECURITY.md exists — audit and verify mitigations
- (B) No SECURITY.md, PLAN.md with threat model exists — run from artifacts
- (C) Phase not executed — exit with guidance
Output: updated SECURITY.md.
</objective>
<execution_context>
@${CLAUDE_PLUGIN_ROOT}/workflows/secure-phase.md
</execution_context>
<context>
Phase: $ARGUMENTS — optional, defaults to last completed phase.
</context>
<process>
Execute @${CLAUDE_PLUGIN_ROOT}/workflows/secure-phase.md.
Preserve all workflow gates.
</process>
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Java Spring Boot 服务中关于身份验证/授权、验证、CSRF、密钥、标头、速率限制和依赖安全的 Spring Security 最佳实践。