agentsclimarketplace

Supply chain pinning

Skill 26zl/universal-agent-skills/skills/supply-chain-pinning

Canonical Agent Skills with idempotent cross-agent installers for Claude Code, Codex, OpenCode, and GitHub Copilot

Install
npx -y skills add 26zl/universal-agent-skills --skill supply-chain-pinning

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 14 days oldThe repository was created 14 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Add dependencies deliberately by justifying each new one, pinning versions or commits, respecting lockfiles, and never executing unpinned remote code. Use when adding or updating packages, container images, GitHub Actions, install scripts, or vendored code; do not use to block upgrades the user explicitly requested.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.5 KB, as published. Nobody here has run it

Supply Chain Pinning

Every dependency is code you now ship; adopt it deliberately or not at all.

Rules

  • Before adding a dependency, state what it is needed for and why the standard library or an existing dependency does not cover it.
  • Pin what you adopt: exact versions in manifests where the ecosystem supports it, full commit hashes for Git sources and GitHub Actions, digests for container images.
  • Never pipe remote scripts into a shell and never fetch install code from a mutable reference; when a script install is unavoidable, download, review, and execute it from disk.
  • Respect lockfiles: change them through the ecosystem's own tool, never by hand, and never delete one to make an install pass.
  • Read what changed before adopting an update; a major version bump or a maintainer change is a review event, not a routine edit.
  • Prefer maintained dependencies with compatible licenses over unmaintained or trivially replaceable packages.

Boundaries

  • Explicitly requested upgrades proceed; this skill shapes how they happen, not whether.
  • Ecosystems without real pinning support get the strictest available constraint plus a note about the residual risk.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.