incident-response
Audited by Socket on Oct 29, 2026
2 alerts found:
SecurityAnomalyThe skill’s incident-response purpose and data flows are broadly coherent, with no evidence of malware, credential harvesting, or an untrusted install chain. Its handsfree, zero-question approach is disproportionate for production actions that can disrupt service or alter evidence, so require user confirmation before consequential changes or external communications.
No direct malicious behavior or obfuscated payload is present in the supplied YAML. The configuration grants broad command execution and file modification privileges, creating a moderate security risk that depends on the omitted SKILL.md and runtime safeguards. Review the referenced procedure and enforce least privilege, command approval, path restrictions, and secret-handling controls.