auditoria-supply-chain

Audit local persistence, credentials, and package inventories for supply-chain compromise.

5|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill auditoria-supply-chain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auditoria-supply-chain
Source: https://github.com/rafael-fae/agent-ops-worflow/tree/main/archive/skills/security/auditoria-supply-chain
Command: npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill auditoria-supply-chain

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about auditoria-supply-chain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my local environment for npm or pypi supply chain compromise?

To audit for supply chain compromise, you need to inspect local persistence locations, validate installed package inventories against known IOCs, and check for malicious typosquatting heuristics.

What is the best way to find exposed credentials after a package ecosystem security incident?

Finding exposed credentials after a security incident requires mapping stored tokens across environment files, application profiles, and PM2 configurations to identify which Slack, GitHub, or API keys need rotation.

How do I check for malicious hooks in VS Code or Claude Code configurations?

Checking for malicious hooks involves inspecting common local persistence points like Claude and VS Code configuration directories to detect suspicious settings or unauthorized automation scripts left by compromised packages.

Can I use this approach to plan token rotation for Slack and GitHub?

Yes, you can use this approach to plan token rotation for Slack and GitHub by following dedicated rotation playbooks that include backup procedures, credential revocation, and validation steps to secure the environment safely.

Does the supply chain audit process require a specific tool to compare installed packages against threat intelligence?

Yes, the supply chain audit process requires a dedicated Python audit script to cross-verify installed package inventories against manually curated IOCs and typosquatting signals to detect potential threats accurately.

When should I investigate PM2 configuration files during a security audit?

You should investigate PM2 configuration files during a security audit when you need to inventory exposed credentials, as compromised packages often target environment variables and tokens stored within process management setups.