T08 · Insecure Dependencies
- Location
SKILL.md:17- Finding
Unpinned npm Dependency May Execute Unreviewed Supply-Chain Code
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent AgentFiles wrapper, but it can install mutable npm code and transmit/share conversation or artifact content with under-specified safety controls.
Review the exact AgentFiles recipient, namespace, and payload before approving any publish or handoff. Treat share URLs and API keys as secrets, avoid command-line API keys where possible, use watch --exec only with trusted scripts, and prefer a pinned or administrator-installed agentfiles CLI rather than downloading the latest npm package at runtime.
SKILL.md:17Unpinned npm Dependency May Execute Unreviewed Supply-Chain Code
installable/handoff/SKILL.md:17Handoff Workflow May Publish Excessive or Sensitive Conversation Content
The skill explicitly allows falling back to npx/npm to obtain and run agentfiles-cli without pinning a specific version. That creates a supply-chain risk: a compromised package, typosquat, or unexpected upstream update could be executed at runtime with the user's privileges. In this skill context, the danger is elevated because the tool is intended to handle artifacts, credentials, and networked operations, so executing an unpinned remote CLI can expose local data or auth context.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- Always use the `artifact_publish` MCP tool. Do not shell out to the CLI.
- Ask the user for confirmation before publishing the handoff artifact.
- Keep the content focused and actionable. The recipient agent should be able to pick up the work without extra context.
- If no namespace is configured, the MCP server will use the default. Do not ask the user for a namespace unless the publish fails.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- Always use the `artifact_publish` MCP tool. Do not shell out to the CLI.
- Ask the user for confirmation before publishing the handoff artifact.
- Keep the content focused and actionable. The recipient agent should be able to pick up the work without extra context.
- If no namespace is configured, the MCP server will use the default. Do not ask the user for a namespace unless the publish fails.
The share command creates a temporary share token and preview URL, which are access-bearing secrets, but the command matrix does not warn that anyone with the tokenized URL may be able to access the artifact until expiry. In a file-sharing skill, this is especially relevant because users may copy tokens into chats, tickets, or logs without realizing they grant access.
The watch --exec ./script mode will execute a local program for each event, but the documentation does not prominently warn about the code-execution behavior or the risks of feeding untrusted event data into automation. In an agent-oriented skill, this is more dangerous because users are likely to wire it into unattended workflows where event-triggered execution can amplify mistakes or unsafe wrapper scripts.
The documentation includes a direct configuration command that places an API key on the command line without warning that shell history, process listings, logs, or transcripts may capture the secret. In a skill intended for agent runtimes and automation, that omission increases the chance that users or wrappers will handle long-lived credentials unsafely.
No suspicious patterns detected.