dependency-vetting SKILL.md skillA
dependency-vetting from svyatov/supermatt is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add svyatov/supermatt/dependency-vetting@git:20261011.62c7072Pins git:20261011.62c7072 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- svyatov/supermatt
- Path
skills/dependency-vetting/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261011.62c7072, committed Oct 11, 2026
- First version recorded
- Sep 30, 2026
- Size
- 2,631 bytes
- Repository stars
- 14
- License
- MIT
Verify a package or tool is authentic before installing, adding, upgrading, or recommending it. Use whenever a task would add a dependency to a project, suggest a CLI tool, or pull a package from npm, PyPI, crates.io, Go modules, RubyGems, Homebrew, or any other registry. Also use when a registry page, install command, or installed artifact looks inconsistent with the project that supposedly publishes it.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Dependency vetting The rule: never install, add, or recommend a package until you have opened the upstream project's own repo or docs and used the install command or import path published there. The sections below are the full reasoning behind it. ## Direction of trust Follow the link **from the upstream project to the install command**. Never work the other direction, from a search result or a registry page back to a project. Treat unverified registry metadata as publisher-supplied claims: author, email, homepage, repository link, README, and license. Where the registry independently verifies a field or attestation, check what that verification establishes and compare the verified identity with the intended upstream project. Still open the upstream repository or docs and confirm the published installation instructions. If upstream documents no registry install, then there is no registry package, whatever the registry shows. Stop and say so. Do not install it, do not pin around it, and do not quietly swap in an alternative. Pinning untrusted code to a SHA is the same code with better bookkeeping, not a fix. ## Registry signals worth using …
Read the whole file at its exact version.
How to install
mdr add svyatov/supermatt/dependency-vetting@sha256:c52c4c7350b7e1afThe line at the top of this page pins the label git:20261011.62c7072, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_yx36mm46iilfvdyx)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 30, 2026 and Oct 11, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261011.62c7072 latest | 2026-10-11 | 62c7072 | 2,631 B | A | view · diff |
| git:20260930.ca70280 | 2026-09-30 | ca70280 | 2,539 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2631 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
svyatov/supermatt · 14 stars · license MIT · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yx36mm46iilfvdyx GET https://markdownregistry.com/api/v1/resolve?ref=svyatov/supermatt/dependency-vetting GET https://markdownregistry.com/api/v1/blob/c52c4c7350b7e1af42eb62a9e76f1827bf8937abaf047069a002dfe659292852
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.