agentleFS
26zl26zl/universal-agent-skills/skills/supply-chain-pinning/SKILL.md

supply-chain-pinning

Skill2 starsChanged 40 days agoMITView on GitHub

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

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every dependency is code you now ship.

    line 9
  2. Distinctive:

    Before adding a dependency, state what it is needed for and why the standard library or an existing dependency does not cover it.

    line 13
  3. Distinctive:

    Read what changed before adopting an update.

    line 17
  4. Distinctive:

    Prefer maintained dependencies with compatible licenses over unmaintained or trivially replaceable packages.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 it from an immutable URL and check it against a pinned checksum or signature; review the verified local copy before you run it.
  • 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.