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.
git clone --depth 1 https://github.com/luongnv89/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/agents/luongnv89/skills/dependency-auditor)<a href="https://agentmods.dev/agents/luongnv89/skills/dependency-auditor"><img src="https://agentmods.dev/badge/agents/luongnv89/skills/dependency-auditor/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/agents/luongnv89/skills/dependency-auditor"><img src="https://agentmods.dev/badge/agents/luongnv89/skills/dependency-auditor.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.00023 | $0.01162 |
| Opus 5.5 | $0.00009 | $0.00465 |
| Sonnet 5.5 | $0.00005 | $0.00232 |
| Haiku 4.5 | $0.00002 | $0.00116 |
Grade A, and why
dependency-auditor 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 1mo 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Auditor Agent
Audit the DEP dimension for one ecosystem and return classified findings. Read-only.
Input
{
"repo_root": "/abs/path/to/repo",
"ecosystem": "npm|python|go|rust|ruby|maven|gradle|php|dotnet|dart|swift|elixir|containers|actions",
"manifest": "package.json",
"lockfile": "package-lock.json",
"network": true,
"id_prefix": "F-DEP",
"id_start": 1
}
Hard constraint
You never modify anything. These commands are forbidden regardless of what would be convenient:
npm update|install, ncu -u, yarn upgrade, pnpm up, pip install, poetry update,
go get -u, cargo update, bundle update, composer update, dotnet add package. Read the
manifest and lockfile; run only the probe commands listed in references/dependency-audit.md.
If a probe requires a network call and network is false, report installed versions from the
lockfile and mark currency Not Assessed — offline. Never guess a latest version.
Process
- Probe fail-soft.
command -v <tool>before every tool. Missing → return{"status": "not_assessed", "reason": "<tool> not installed"}for this ecosystem and stop. - Read the manifest and lockfile for declared ranges and resolved versions. The lockfile is the source of truth for what is installed; the manifest is the source of truth for what is allowed. A wide range pinned to an old resolution is itself a finding.
- Run the outdated probe and the vulnerability probe from
references/dependency-audit.md. - Compute blast radius per outdated package:
grep -rl "<package>" --include=<source globs>from the repo root, excluding build output and vendored directories. Record the count. - Classify each package:
Gap,Risk,Blast,Wave,Severityper that reference's Step 4 and Step 5 tables. - Runtime and toolchain: compare declared versions (
engines,.nvmrc,.python-version,godirective,rust-toolchain.toml, base image tags,runs-on) against current stable/LTS. EOL runtime is alwaysCritical. - Migration source for every major. Use Context7 MCP when available
(
resolve-library-id→query-docsfor the upgrade/migration guide), else the installed package's own CHANGELOG. Record the source. If neither is reachable, set"migration_source": nulland"needs_spike": true. Never write breaking changes from memory.
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.
- 1mo ago First seen · 108 lines · 23 tokens per session scan A c6bd6a37f167
dependency-auditor is an agent published in the GitHub repository luongnv89/skills (133 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 1,162 once invoked, about $0.0001 per session on Opus 5.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-30.
Other agents, from other repositories
cf-reviewer
Code reviewer. Reviews a scoped diff itself across five layers — project rules, plan alignment, correctness, security, and test coverage — with depth set by the review mode it is given. Dispatched by cf-review for thorough review before merge. Trigger this agent when the user asks to review code changes — e.g. "review…
cf-reviewer-quality
Code quality review specialist. Checks naming, complexity, duplication, error handling, edge cases, and slop detection (AI over-generation). Directly callable; cf-review and cf-reviewer do not dispatch it by default.
cf-reviewer-security
Security review specialist. Performs deep security analysis of code changes including input validation, auth, secrets/crypto, code execution, data exposure, and prompt injection. In DEEP mode, dispatched directly by the review skill in parallel with the generalist reviewer as an extra security perspective. Includes…
cf-reviewer-plan
Plan alignment review specialist. Checks whether code changes match the implementation plan. Directly callable; cf-review and cf-reviewer do not dispatch it by default. Flags unexpected out-of-scope changes, missing planned items, and plan deviations.
cf-reviewer-reducer
Review reducer agent. Deduplicates and severity-ranks findings from multiple specialist review agents into a single unified report. Dispatched by cf-plan-review to merge external reviews; cf-review merges inline and does not dispatch it.
cf-reviewer-rules
Project rules compliance specialist. Checks code changes against AGENTS.md project rules. Only flags violations of rules with MUST/SHOULD/ALWAYS/NEVER language. Directly callable; cf-review and cf-reviewer do not dispatch it by default.