T08 · Insecure Dependencies
- Location
README.md:18- Finding
Unpinned Package Execution and Mutable Global Skill Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill content is a coherent marketing playbook, but its documented install and scan commands rely on mutable unpinned remote execution and a global noninteractive install.
Review the install path before using this skill: pin the installer and scanner versions, install from a reviewed commit or signed release, avoid `--yes` and `--global` unless you deliberately want persistent global availability, and run any package-runner commands in a least-privileged or disposable environment.
README.md:18Unpinned Package Execution and Mutable Global Skill Installation
README.md:24Execution of an Unpinned Latest Security Scanner Package
The skill explicitly says to trigger on ANY marketing, branding, growth, or go-to-market topic and even to use the skill when in doubt. That creates excessive scope and routing collisions, causing the agent to invoke this skill for routine or loosely related conversations where a narrower or more appropriate skill should be selected, which can degrade safety, relevance, and system behavior.
The README instructs users to run npx skills without pinning a specific package version. Because npx resolves and executes the latest matching package by default, a compromised or malicious upstream release could be executed on the user's system during installation. In skill-installation context this is more dangerous because users are likely to copy-paste the command directly and grant it broad trust.
The security scan command uses uvx snyk-agent-scan@latest, which explicitly pulls and executes the latest version at runtime. This creates a supply-chain risk: if the package or a newly published version is compromised, users invoking the scan command may run unreviewed code. The skill context increases risk slightly because the command is presented as a security verification step, which may cause users to trust and execute it without additional scrutiny.
No suspicious patterns detected.