skills sourced live from GitHub · all skills listed are free · each skill is provided under its author's license.
home / Security / Supply Chain Attack Response Skill by @BagelHole
The skill is the security/scanning/supply-chain-attack-response folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.
Detection and response playbooks for software supply chain attacks in packages, containers and CI/CD.
Covers audit commands, lockfile review, provenance checks and emergency steps when a dependency is compromised. Useful as a runbook to rehearse before an incident.
The original SKILL.md is organised into these sections:
Written and maintained by @BagelHole. It is published under the MIT license, which allows reuse with attribution. See the author profile. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.
# Supply Chain Attack Response Software supply chain attacks target the dependencies, build systems, and distribution channels that developers trust implicitly. When a package on PyPI, npm, or crates.io is compromised, every downstream consumer inherits the malicious payload. This skill provides detection techniques, emergency response playbooks, and hardening strategies to protect your software supply chain end to end. --- ## 1. When to Use This Skill Invoke this skill when any of the following apply: - A dependency you consume has been flagged as compromised (e.g., advisories on OSV.dev, GitHub Advisory Database, or vendor disclosure). - You observe suspicious behavior from a dependency: unexpected network calls, file system writes outside its scope, or new post-install scripts. - You are conducting a periodic supply chain security audit. - A CI/CD pipeline is behaving unexpectedly after a dependency update. …
Excerpt only, quoted from the author's repository. Open the repository for the complete file.