Menu
Run a structured security review before marking a task done. Use this for code, config, architecture, or release reviews that need OWASP, baseline pack, and domain-pack coverage.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Run objective, repeatable improvement work under an immutable verifier and hard iteration, cost, time, and no-progress limits. Use for approved experiments with an automated metric and sandboxed worker.
Write concise, calm technical responses whose structure matches the decision, evidence, or sequence being communicated. Use when drafting substantial plans, reviews, findings, documentation, or completion summaries.
Operate inside a ControlKeel-governed session. Use this before code edits, shell execution, delegation, deploy work, or any task that needs CK validation, findings, budget, proof, or routing context.
Keep a governed session within budget. Use this before long-running agent work, bulk processing, or any task where spend pressure could change the plan.
Close a governed work session with validation, proof, findings, budget, digest, learning, and handoff checks. Use when the user asks to wrap up, stop for the day, or leave work ready for another agent.
Audit tests that may pass without proving the claimed behavior. Use for periodic test-quality reviews or when coverage looks healthy but regressions still escape.
| name | security-review |
| description | Run a structured security review before marking a task done. Use this for code, config, architecture, or release reviews that need OWASP, baseline pack, and domain-pack coverage. |
| when_to_use | Use before merging, deploying, or signing off on code, config, or architecture changes. Activate when reviewing auth, input handling, secrets, or third-party dependencies. |
| argument-hint | [file, PR, or area to review] |
| license | Apache-2.0 |
| compatibility | ["codex","claude-standalone","claude-plugin","copilot-plugin","github-repo","open-standard","cline-native","cursor-native","windsurf-native","continue-native","letta-code-native","pi-native","roo-native","goose-native","opencode-native","gemini-cli-native","kiro-native","kilo-native","amp-native","augment-native","hermes-native","multica-native","openclaw-native","devin-terminal-native","warp-native","droid-bundle","forge-acp"] |
| metadata | {"author":"controlkeel","version":"2.1","category":"security","ck_mcp_tools":["ck_validate","ck_context","ck_finding","ck_regression_result"],"related_skills":["agent-pattern-verification"]} |
Use this skill before closing a task, approving a proof bundle, or reviewing a risky diff.
Apply this explicit boundary system during review:
ck_context to load the domain pack, risk tier, open findings, instruction hierarchy, and design-drift signals.ck_validate on the relevant code or config slices, including trust-boundary metadata when the proposed action was influenced by web, tool, skill, or mixed-provenance content.ck_finding, including boundary tier classification in metadata.ck_regression_result when it affects release readiness.When agent frameworks are detected in the workspace context, this skill automatically includes agent-specific pattern checks:
while True without break, recursive calls without depth limitsThese checks complement the baseline security review with agent-specific anti-pattern detection.