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 khasky/awesome-agent-skills --skill awesome-dependency-auditgit clone --depth 1 https://github.com/khasky/awesome-agent-skillsWrote 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/khasky/awesome-agent-skills/awesome-dependency-audit)<a href="https://agentmods.dev/skills/khasky/awesome-agent-skills/awesome-dependency-audit"><img src="https://agentmods.dev/badge/skills/khasky/awesome-agent-skills/awesome-dependency-audit/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/khasky/awesome-agent-skills/awesome-dependency-audit"><img src="https://agentmods.dev/badge/skills/khasky/awesome-agent-skills/awesome-dependency-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 20 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium MCP Rug Pull · line 44 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00117 | $0.03287 |
| Opus 5 | $0.00059 | $0.01643 |
| Sonnet 5 | $0.00023 | $0.00657 |
| Haiku 4.5 | $0.00012 | $0.00329 |
Grade A, and why
awesome-dependency-audit scanned grade A with 1 finding 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 yesterday.
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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Provenance and the published artifact — where the registry supports it, verify signatures (`npm audit signatures`, sigstore attestations) and prefer packages that publish from a traceable build. Read what actually ship How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Audit
Audit the third-party dependency graph — manifests, lockfiles, and the packages they resolve to — for supply-chain risk, before it ships with the product. Read-only: it reports findings and a verdict; it does not upgrade, pin, or remove anything. To act on the report, call the Skill tool with "awesome-dependency-upgrade".
Two phases: passive (reading manifests, lockfiles, license files, changelogs already on disk — no gate) and active (anything that reaches a registry or scanner: npm audit, pip-audit, osv-scanner, registry metadata lookups — propose the commands and wait for approval first). Default to passive; say what staying passive leaves unverified.
Scope and method
- Establish scope — the whole graph, one manifest, or one diff (a bot bump, a new package). Name the ecosystems found (
package.json,requirements.txt/pyproject.toml,go.mod,Cargo.toml,pom.xml/gradle,Gemfile). Include the repo's agent extensions in the graph when present —.claude/,.agents/,.cursor/,.gemini/skill and plugin folders,.mcp.jsonand equivalent MCP server lists, plugin-marketplace references, and any agent hook manifest. They install and execute on a contributor's machine exactly like a dependency, and no scanner covers them (Track C). - Gather evidence — manifests + lockfiles + install configuration (
.npmrc,pip.conf, registry settings) + CI install commands. Every finding cites a file, a line, a version, or a scanner line — no "this package feels risky". - Walk the five tracks below — a track whose signal you cannot observe (no lockfile committed, no registry access approved) is
NOT ASSESSED, never a guess. - Score, gate, report — one SHIP / FIX / BLOCK verdict for the audited scope. See Output.
Done when: every ecosystem manifest found is named, each of the five tracks carries findings or a NOT ASSESSED with its reason, and every finding cites a file, a version or a scanner line.
Parallelizing the passive tracks (large graph). Tracks A–E are independent lenses, and Tracks B (name authenticity) and C (health/provenance) are per-package — embarrassingly parallel. Fan out read-only sub-agents: one per ecosystem manifest, or one per batch of newly-added packages for the per-package tracks, each reading manifests, lockfiles, and unpacked tarballs off disk. Keep every active step in the parent — a sub-agent must never run a Track-D scanner or reach a registry, those are gated once (the passive/active split) by the parent, not N times by N agents. Barrier before the verdict: the parent dedupes to one finding per package@version and resolves transitive license/CVE reachability, which is graph-wide, not per-package. Resource preflight (before fan-out): cap concurrency at min((cores−1)×0.75, free_gb×0.7/per_agent, 6), per_agent ≈ 0.7 GB for read-only agents; go serial if CPU load > 85% or free RAM < 2×per_agent; recompute before each wave; where the runtime caps sub-agent concurrency itself, defer to it.
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.
- yesterday Changed b233dcb7f3ca
- 5d ago Changed · +2 lines · -60 tokens per session 0926a6b3ac22
- 12d ago First seen · 117 lines · 177 tokens per session scan A 22719e67ca29
awesome-dependency-audit is a skill published in the GitHub repository khasky/awesome-agent-skills (8 stars, last pushed yesterday), licensed MIT. It adds 117 tokens to every session and 3,287 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
cukaimax-tax-authority
Research Malaysian individual tax rules, explain Form BE or Form B, prepare source-linked YA2025 Form BE drafts, assess public Form B preparation readiness, hand private Form B work to the authenticated CukaiMax app, and plan for YA2026 through the CukaiMax MCP. Use when a user asks about Malaysian personal income…
open-source-checker
Audits a whole private repository once, at the decision to make it public. Runs four passes — license and attribution, secrets across the entire git history, private references (internal hostnames, employee emails, client and customer names, staging URLs), and publication readiness — then returns a publish or block…
expense-review-policy
Review invoices and contracts against accounts-payable policy before human approval.
idea-refine
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…
9router-web-fetch
Fetch URL → markdown / text / HTML via 9Router /v1/web/fetch using Ollama Cloud / Firecrawl / Jina Reader / Tavily Extract / Exa Contents. Use when the user wants to scrape a webpage, extract URL content, read article, or convert a URL to markdown.
9router-web-search
Web and X search via 9Router /v1/search using Tavily / Exa / Brave / Serper / SearXNG / Google PSE / Linkup / SearchAPI / You.com / Perplexity / Xquik. Use when the user wants to search the web, find articles, or search public X posts.