supply-chain-risk-auditor
Skill1 starsChanged 33 days agoMITView on GitHub
Assess dependency provenance, maintenance, release trust and exposure to known compromises using authoritative evidence and exact installed versions.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- Big-LAORE/Biblioth-que-de-skillstheir own version, first seen Nov 1, 2026
- davidanthonyn/claude-skillstheir own version, first seen Oct 20, 2026
- matheus-rib1108/meu-kit-claude-codetheir own version, first seen Oct 17, 2026
- waybarrios/opencode-power-packtheir own version, first seen Oct 13, 2026
- Egoushka/agent-skillstheir own version, first seen Sep 26, 2026
- romaintoso78/claude-skillstheir own version, first seen Jun 25, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- waybarrios/opencode-power-pack★ 547same name
- Big-LAORE/Biblioth-que-de-skills★ 1same name
- romaintoso78/claude-skills★ 1same name
- davidanthonyn/claude-skills★ 0same name
- Egoushka/agent-skills★ 0same name
- matheus-rib1108/meu-kit-claude-code★ 0same name
- TheWatcher01/skills★ 0same 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 repository42 other files it gives its agents.
- ansible-hardeningSkill
- cavetechSkill
- ci-cdSkill
- claude-to-cursorSkill
- code-consistencySkill
- code-qualitySkill
- config-auditorSkill
- container-sandboxSkill
- cpa-tax-specialistSkill
- database-designSkill
- definition-of-doneSkill
- differential-reviewSkill
- exact-head-reviewSkill
- fast-ciSkill
- grill-meSkill
- inbound-syncSkill
- infosec-architectSkill
- insecure-defaultsSkill
- lonely-sysadminSkill
- mcp-createSkill
- mcp-hardeningSkill
- model-evaluationSkill
- modern-pythonSkill
- ms-office-suiteSkill
- mutation-checkSkill
- plan-to-execution-handoffSkill
- prd-to-planSkill
- property-based-testingSkill
- pr-truth-triageSkill
- repo-hardening-workflowSkill
- resume-writerSkill
- skill-updaterSkill
- software-developerSkill
- software-development-lifecycleSkill
- solutions-architectSkill
- stay-readySkill
- systematic-debuggingSkill
- tddSkill
- token-miserSkill
- triage-issueSkill
- verification-before-completionSkill
- write-a-prdSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Use the available repository connector, package registry metadata and current vendor advisories.
- Distinctive: line 15
Write a report using the report template.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Supply-chain risk audit
Inventory direct and transitive dependencies from actual lockfiles, installed artifacts and build inputs. Record package ecosystem/name/version, source URL, integrity/provenance, execution phase, permissions and reachable consumer. Include CI actions and install scripts.
Use the available repository connector, package registry metadata and current vendor advisories. A missing gh binary need not block other authorized evidence gathering. Do not install or execute a suspicious package to inspect it.
Assess maintainer/release access controls, provenance, ownership transfers, unusual release changes, supported versions, response to verified vulnerabilities and dangerous capabilities. Popularity, anonymity, number of maintainers or raw CVE counts are signals for investigation, not proof of maliciousness or a standalone high-risk verdict.
Match advisories to exact affected versions and artifact digests. Check whether affected code ran and what credentials/data it could reach. Follow incident verification and indicator handling. A name/string match alone is not confirmation; a missing match is not proof of safety.
Write a report using the report template. Include the complete assessed inventory or a coverage summary so omitted packages are not interpreted as safe. Distinguish confirmed exposure, risk needing investigation, no finding within scope and unavailable evidence.
Recommend proportional fixes, verified supported alternatives and a migration/test plan. Preserve evidence and follow the authorized incident-response process before disruptive containment, credential rotation or reinstall. Do not prescribe a stale 'safe version' from a static skill file.
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.

