Security Core

Shared reference for the security cluster: the trust-boundary model (untrusted input/action → privileged sink), the defend-vs-attack × code/config/runtime surface map, severity & exploitability conventions, and the tooling matrix every security spoke shares. USE WHEN triaging a finding, judging whether something is exploitable, or deciding which control to apply — the interlocking rules behind all six spokes.

Sheshiyer Updated

File contents

Sheshiyer/skill-clusters commit 7b240135cd

Frequently asked questions

npx get-skill add sheshiyer/security-core