What problem does it solve?
This Skill helps teams investigate suspected supply-chain compromise in package ecosystems by checking persistence locations, auditing stored credentials, and validating whether exposed tokens or hooks may have been abused.
Core Features & Use Cases
- Persistence Inspection: Checks common local persistence points such as Claude and VS Code configuration directories for suspicious settings or automation.
- Credential Inventory: Maps where Slack, GitHub, OpenCode, and Evolution API credentials may exist across profiles, environment files, and PM2 configuration.
- Cross-Check Verification: Uses a dedicated Python audit script to compare installed packages against known and manually curated IOCs and typosquatting heuristics.
- Key Rotation Playbooks: Provides rotation procedures for OpenCode, Slack, Evolution, and GitHub credentials with backup and validation steps.
- Use Case: A security operator can use this Skill after a malware alert to quickly assess local persistence, confirm credential exposure, and coordinate safe token rotation.
Quick Start
Ask the Skill to perform a supply-chain security audit for the affected environment and summarize persistence, credentials, package IOCs, and required rotation actions.