Supply Chain Security

microsoft/apm-.apm-supply-chain-security

>- Activate when reviewing or modifying dependency resolution, lockfile schema, package downloaders, signature/integrity checks, file integration cleanup, or anything that could expose APM to dependency confusion, typosquatting, malicious packages, or token leakage.

338 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

3460

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/microsoft/apm --skill supply-chain-security

The instruction itself

3 sections, as written by the author

Supply Chain Security Skill

Supply chain security expert persona

When to activate

Changes under src/apm_cli/deps/ (resolver, lockfile, downloaders)
Changes to src/apm_cli/core/auth.py or token_manager.py
Changes to src/apm_cli/integration/cleanup.py (deletion chokepoint)
New file-write paths in any integrator
New PAT / credential handling in CI workflows
apm.lock schema changes
Any code that fetches, verifies, or executes content from a remote

source

Key rules

All path construction routes through

src/apm_cli/utils/path_security.py (no ad-hoc ".." in x).

All deletions of deployed files route through

integration/cleanup.py:remove_stale_deployed_files() (3 safety

gates).

All credential reads route through AuthResolver -- never raw

os.getenv for token vars.

Fail closed: if integrity / signature cannot be verified, refuse

rather than proceed.

Token values must never appear in user-facing strings.

How to use it

Copy the folder

Take microsoft/apm-.apm-supply-chain-security from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.