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 skills/lyupro/skillforge-mcp/dependency-checkernpx skills add lyupro/skillforge-mcp --skill dependency-checkergit clone --depth 1 https://github.com/lyupro/skillforge-mcpWrote 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/lyupro/skillforge-mcp/dependency-checker)<a href="https://agentmods.dev/skills/lyupro/skillforge-mcp/dependency-checker"><img src="https://agentmods.dev/badge/skills/lyupro/skillforge-mcp/dependency-checker.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.00023 | $0.00320 |
| Opus 5 | $0.00012 | $0.00160 |
| Sonnet 5 | $0.00005 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
dependency-checker 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 4d 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
This is a script-strategy skill. The script in scripts/main.sh runs npm audit --json inside the directory supplied via SKILLFORGE_INPUT (or the SkillForge temp cwd if input is empty), parses the output with jq, and prints a one-line summary to stdout.
Output format (one line):
high=<N> critical=<M> total=<T> packages=<P>
When npm audit errors (no package.json, no node_modules, network failure), the script prints error=<reason> and exits 0 — SkillForge returns the line as a successful invocation, the consuming agent decides what to do with the diagnostic.
Prerequisites:
config.security.allowScripts: truein the SkillForge persisted config.npmandjqon the host's resolvedPATH(on POSIX, the SandboxRunner restrictsPATHto/usr/bin:/bin— installjqsystem-wide or overrideDEFAULT_PATHfor this skill).SKILLFORGE_INPUTset to an absolute path of the project to audit, or unset to audit the temp cwd (which will report nopackage.json— usually pass the path explicitly).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 27 lines · 23 tokens per session scan A 2557e8cd821b
dependency-checker is a skill published in the GitHub repository lyupro/skillforge-mcp (1 stars, last pushed 20d ago), licensed MIT. It adds 23 tokens to every session and 320 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 skills, from other repositories
depsguard
Install and run DepsGuard, a zero-dependency CLI that scans and fixes package manager configs (npm, pnpm, yarn, bun, uv) for supply chain security best practices.
dep-audit
Audit and update project dependencies: find outdated packages, check for vulnerabilities, auto-update safely with lockfile regeneration.
upgrade-packages-js
Safely upgrade JavaScript packages with breaking change detection, migration guidance, and automated code migrations (npm/pnpm/yarn). Cross-platform with git safety branch enforcement.
dependency-manager
Manage project dependencies — update packages, audit vulnerabilities, resolve conflicts, and keep dependencies healthy. Use when updating packages, fixing vulnerability alerts, or resolving dependency issues.
opendia-harness
Install, configure, and troubleshoot OpenDia for Grok Build (and other MCP harnesses). Use when setting up the plugin, config.toml MCP entry, ports, extension disconnects, tool timeouts, or tunnel mode.
ship-safe-fix
Auto-fix security issues — remediate hardcoded secrets and common vulnerabilities (TLS bypass, debug mode, XSS, shell injection, Docker :latest). Use when the user wants to automatically fix security findings.