Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add yongquantan/dependency-guard --skill supply-chain-reviewgit clone --depth 1 https://github.com/yongquantan/dependency-guardWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/yongquantan/dependency-guard/supply-chain-review)<a href="https://agentmods.dev/skills/yongquantan/dependency-guard/supply-chain-review"><img src="https://agentmods.dev/badge/skills/yongquantan/dependency-guard/supply-chain-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/yongquantan/dependency-guard/supply-chain-review"><img src="https://agentmods.dev/badge/skills/yongquantan/dependency-guard/supply-chain-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00362 |
| Opus 5 | $0.00000 | $0.00181 |
| Sonnet 5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
supply-chain-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Supply Chain Review
When the user asks about dependency security, supply chain hardening, or wants to review the safety of their installed packages, use this skill.
What to check
- Lockfile integrity — Are
package-lock.json/yarn.lock/uv.lockcommitted and up to date? - Pinned versions — Are dependencies pinned to exact versions (not ranges)?
- Install scripts — Run
npm pkg get scripts.postinstallor checksetup.pyfor install-time code execution. - Known vulnerabilities — Run
npm auditorpip auditif available. - Forensic logs — Check
~/.dep-guard/logs/for recent audit logs from Dependency Guard.
Recent attack patterns to watch for
- Phantom dependencies: A package adds a dependency that doesn't exist on the registry, then publishes it with malware (e.g., axios + plain-crypto-js).
- Postinstall RATs: Malicious code in postinstall hooks that phones home and drops a remote access trojan (e.g., LiteLLM .pth file attack).
- Typosquatting: Packages with names similar to popular ones (e.g.,
axoisinstead ofaxios). - Credential harvesting: Postinstall scripts that read ~/.ssh, ~/.aws, or environment variables and exfiltrate them.
Hardening recommendations
- Disable install scripts globally:
npm config set ignore-scripts true(re-enable per package as needed) - Use
--ignore-scriptsflag for installs of unfamiliar packages - Pin all dependency versions and commit lockfiles
- Review diffs when lockfiles change in PRs
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 27 lines · 0 tokens per session scan A e0167e84c400
supply-chain-review is a skill published in the GitHub repository yongquantan/dependency-guard (7 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 362 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
setup
Scaffold project: clone repo, install real library. Only invoke when explicitly requested by the user or by the yoink orchestrator.
yoink
Curate tests then decompose dependencies.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Plugin Settings
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md…
api-debugging
Systematic approach to debugging REST APIs, HTTP errors, authentication issues, and network problems. Use when the user has API errors, status code issues, timeout problems, or needs help troubleshooting HTTP requests.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.