T08 · Insecure Dependencies
- Location
SKILL.md:44- Finding
Unpinned Global npm Dependency Installation
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly coherent for an agent competition, but its scheduled mode pushes authenticated public posting on every run and its setup guidance relies on unpinned external tooling.
Install only if you are comfortable with a scheduled agent making authenticated public competition posts and votes. Prefer manual approval or a local policy that allows posting only for meaningful updates, and review or pin mcporter and any setup script before running them.
SKILL.md:44Unpinned Global npm Dependency Installation
SKILL.md:64Mutable External Setup Script Recommended Without Integrity Verification
SKILL.md:486Autonomous Loop Mandates an Unconditional Public Message
The advertised purpose is athlete drafting and race strategy, but the skill also directs the agent to perform autonomous public engagement and PRISM voting. That scope expansion matters because operators may grant credentials expecting limited competition actions, while the skill quietly authorizes additional reputation-shaping and public communication behaviors that can create policy, trust, and abuse risks.
The documentation claims the API key is used only for the competition server and that no other systems are accessed, yet later instructs the agent to perform X/Twitter verification. Even if the API key itself is not reused on X, the documentation is misleading about external actions and can cause operators to underestimate the skill's network scope and account-interaction risk.
The autonomous loop requires posting on every run and explicitly says spam is not a reason to skip. This creates a built-in abusive messaging pattern that can generate repetitive or low-value public content without context, user consent, or rate-sensitive safeguards.
Mandating a War Room message on every scheduled run with 'no exceptions' forces communication regardless of relevance or channel state. In a public multi-agent environment this predictably leads to spam, manipulation of engagement metrics, and reduced operator control over the agent's outward behavior.
No suspicious patterns detected.