T08 · Insecure Dependencies
- Location
SKILL.md:591- Finding
Unpinned Third-Party Installation Commands Create a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 591-592
Vulnerability Type: Unpinned third-party package and remote Skill installation
Risk Level: MediumVulnerable Code
bash npx skills add AgentPMT/agent-skills --skill what-is-agentpmt npx skills add AgentPMT/agent-skills --skill agentpmt-account-mcp-rest-api-setupEquivalent unpinned installation instructions also appear at
SKILL.md:481,SKILL.md:585, andSKILL.md:642-643.Technical Analysis
The documented setup process invokes the
skillsnpm package throughnpxwithout specifying an immutable package version. It then installs Skill content fromAgentPMT/agent-skillswithout pinning that source to a reviewed commit, release, or cryptographic digest.Consequently, the artifacts resolved when a user runs these commands may differ from those available during this audit. The effective installation payload remains under the control of external package and repository publishers. Compromise of the npm package, source repository, publisher credentials, release process, or dependency chain could cause users to retrieve unreviewed content.
The audited project itself contains only documentation and schemas; no embedded malicious script was identified. The risk arises when users follow the external installation commands.
Attack Path
- An attacker compromises the npm package, the
AgentPMT/agent-skillsrepository, a publisher account, or an upstream release dependency. - The attacker publishes a modified latest package or changes the remotely resolved Skill content.
- A user follows the unpinned
npx skills add ...instructions fromSKILL.md. npxresolves the package available at execution time, and the installer retrieves the mutable remote Skill content.- The altered installer or Skill executes or introduces attacker-controlled behavior under the permissions available to the invoking user or agent environment.
Impact Assessment
Successful ...[truncated 537 chars]
- An attacker compromises the npm package, the
- Remediation
View remediation
Remediation Suggestions
- Pin the npm package to an explicitly reviewed version rather than relying on dynamic resolution, for example:
bash npx skills@<reviewed-version> add ... - Pin
AgentPMT/agent-skillsto an immutable commit hash or signed release instead of a mutable repository state. - Publish and verify cryptographic checksums or signatures for downloaded packages and Skill artifacts.
- Configure npm to use a trusted registry and require lockfile integrity where applicable.
- Review retrieved Skill content before enabling it, especially any scripts, setup instructions, network destinations, and credential-handling behavior.
- Run installation in a least-privileged sandbox without production credentials or broad filesystem access.
- Document the exact approved package version, repository commit, expected digest, and verification procedure directly in
SKILL.md. - Replace duplicate unpinned commands at
SKILL.md:481,SKILL.md:585, andSKILL.md:642-643with the same immutable, verified references.
- Pin the npm package to an explicitly reviewed version rather than relying on dynamic resolution, for example:
