dependency-supply-chain
Skill2 starsChanged 33 days agoMITView on GitHub
Reviews young or low-provenance package adds; requires Captain approval and lockfile discipline
1 other project uses a version of this.
Adopted by
Most recently taken up by
- GoldenWing-360/claude-security-skillstheir own version, first seen May 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- GoldenWing-360/claude-security-skills★ 16same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository52 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/00-core-operating-model.mdcCursor rule
- .cursor/rules/01-plan-approval-gate.mdcCursor rule
- .cursor/rules/02-git-worktree-policy.mdcCursor rule
- .cursor/rules/03-validation-definition-of-done.mdcCursor rule
- .cursor/rules/04-documentation-memory.mdcCursor rule
- accessibility-reviewSkill
- agent-skills-packagingSkill
- autonomy-budgetSkill
- bounded-autonomySkill
- candidate-promotionSkill
- capability-planningSkill
- code-reviewerSkill
- code-structure-cleanupSkill
- compass-evaluatorSkill
- context-inodesSkill
- docker-cloudSkill
- embedding-providersSkill
- execution-telemetrySkill
- experience-routingSkill
- experience-skill-trainingSkill
- external-knowledge-ingestSkill
- github-integrationSkill
- goose-agent-orchestrationSkill
- harness-gcSkill
- hosted-vector-dbSkill
- implementation-planningSkill
- ios-engineeringSkill
- knowledge-stewardSkill
- linear-integrationSkill
- node-engineeringSkill
- northstar-connected-routineSkill
- notion-integrationSkill
- package-registry-tiSkill
- persistent-role-promotionSkill
- playwright-browser-validationSkill
- postgres-prismaSkill
- procedure-playbooksSkill
- project-overseerSkill
- pull-request-preparationSkill
- python-mlSkill
- react-engineeringSkill
- repository-discoverySkill
- review-fix-loopSkill
- security-audit-proceduresSkill
- security-reviewSkill
- skill-learning-loopSkill
- skill-lifecycleSkill
- source-code-contextSkill
- technology-intelligence-liveSkill
- testing-validationSkill
- worktree-orchestrationSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Treat a package as higher risk when any of the following appear true (guidance — Captain may still approve):
- Distinctive: line 20
No lockfile in the consuming project
- Distinctive: line 28
Check lockfile presence (or language equivalent) and keep it updated.
- Distinctive: line 29
Prefer well-known, pinned versions.
- Very specific: line 30
Run available audit tooling when present (npm audit, OSV, etc.) and record output under .agent/evidence/ (scrub secrets).
- Very specific: line 32
Prefer source-as-context (source-code-context / opensrc) before guessing APIs.
- Distinctive: line 33
Stop and ask the Captain: before adding higher-risk packages.
- Distinctive: line 35
If scope expands to new deps not in the plan, return to the approval gate.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Dependency Supply Chain
Use this Skill when
Adding or upgrading third-party packages (npm, PyPI, SwiftPM, crates, etc.), especially unfamiliar or newly published libraries.
Labeled guidance (not hard blocks)
Treat a package as higher risk when any of the following appear true (guidance — Captain may still approve):
- Published / first release younger than ~90 days
- Fewer than ~500 GitHub stars (or equivalent signal) when that metric applies
- No lockfile in the consuming project
- Maintainer / provenance unclear; binary-only releases; unusual install scripts
These thresholds are labeled guidance, not automated hook denials.
Procedure
- Identify packages being added or major-upgraded.
- Check lockfile presence (or language equivalent) and keep it updated.
- Prefer well-known, pinned versions; record why a young package is needed.
- Run available audit tooling when present (
npm audit, OSV, etc.) and record output under.agent/evidence/(scrub secrets). - Prefer source-as-context (
source-code-context/ opensrc) before guessing APIs. - Stop and ask the Captain before adding higher-risk packages. Do not add them unilaterally inside an approved plan unless the plan explicitly listed them.
- If scope expands to new deps not in the plan, return to the approval gate.
Output
Risk notes, audit evidence paths, and Captain decision record.
Prohibited actions
- Adding higher-risk packages without Captain acknowledgment
- Committing secrets or tokens from registry tooling
- Weakening lockfiles to force installs
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
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.