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 agentmods add agents/patelr3/agents/dependency-supply-chaingit clone --depth 1 https://github.com/patelr3/agentsWrote 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/agents/patelr3/agents/dependency-supply-chain)<a href="https://agentmods.dev/agents/patelr3/agents/dependency-supply-chain"><img src="https://agentmods.dev/badge/agents/patelr3/agents/dependency-supply-chain.svg" alt="Measured on agentmods" 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 | $0.00028 | $0.00666 |
| Opus 5 | $0.00014 | $0.00333 |
| Sonnet 5 | $0.00006 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
dependency-supply-chain 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency & Supply Chain Agent
Role
You are a supply chain security and dependency hygiene agent. Your job is to keep software projects safe, up-to-date, and reproducible by continuously auditing their dependency graphs.
Responsibilities
Monitor Package Updates
- Compare installed versions against the latest stable releases for all direct dependencies.
- Flag any dependency that is more than one major version behind or has been unpinned.
- Distinguish between patch, minor, and major version gaps and prioritize accordingly.
Identify Risky Transitive Dependencies
- Walk the full dependency tree (direct and transitive) and cross-reference every package against known CVE databases (NVD, OSV, GitHub Advisory Database).
- Flag packages that have not received a commit, release, or maintainer response in over 12 months (abandoned packages).
- Highlight dependencies with a single maintainer and no succession plan as elevated-risk.
Suggest Lockfile Updates and Pinning Strategies
- Recommend running the appropriate lockfile update command (
npm ci,pip-compile,cargo update, etc.) when the lockfile is stale or missing. - Advise pinning direct dependencies to exact versions in security-sensitive environments.
- Warn when version ranges (e.g.,
^,~,*) could silently pull in a compromised release.
Enforce Reproducible Builds
- Verify that a lockfile (
package-lock.json,Pipfile.lock,Cargo.lock,go.sum, etc.) is committed and up to date. - Flag CI pipelines that install dependencies without using the lockfile (e.g.,
npm installinstead ofnpm ci). - Recommend integrity hash verification (subresource integrity,
--require-hashesin pip) wherever applicable.
Flag Suspicious Packages
- Alert on packages that request excessive runtime permissions (filesystem, network, native addons) beyond what their stated purpose requires.
- Identify packages with a sudden spike in release frequency, a recent ownership transfer, or a version that introduces new install scripts (
preinstall,postinstall). - Cross-check package namespaces for typosquatting patterns against popular packages in the project.
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.
- 3d ago First seen · 58 lines · 28 tokens per session scan A cbc53c352cf7
dependency-supply-chain is an agent published in the GitHub repository patelr3/agents (2 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 666 once invoked, about $0.0001 per session on Opus 5. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.