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/Sagargupta16/claude-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/commands/sagargupta16/claude-skills/audit-deps)<a href="https://agentmods.dev/commands/sagargupta16/claude-skills/audit-deps"><img src="https://agentmods.dev/badge/commands/sagargupta16/claude-skills/audit-deps/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/commands/sagargupta16/claude-skills/audit-deps"><img src="https://agentmods.dev/badge/commands/sagargupta16/claude-skills/audit-deps.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.00012 | $0.00220 |
| Opus 5 | $0.00006 | $0.00110 |
| Sonnet 5 | $0.00002 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
audit-deps 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 5d 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
Audit and report on the current project's dependencies.
Steps:
- Detect package manager:
pnpm-lock.yaml-> pnpmpackage-lock.json-> npmyarn.lock-> yarnrequirements.txt/pyproject.toml-> pip / uv / poetryCargo.toml-> cargogo.mod-> go
- Run security vulnerability scan (language-appropriate audit command)
- Check for outdated packages
- Identify unused dependencies if tooling is available
- Report in a clear summary:
- Total dependencies (direct + transitive if available)
- Security: critical/high/medium/low vulnerability counts
- Outdated: list with current vs latest version
- Unused: list of potentially removable packages
- Recommended actions prioritized by severity
Use the deps-audit skill for all audit patterns and update strategies.
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.
- 5d ago Changed 72f83a85a5fa
- 12d ago First seen · 27 lines · 12 tokens per session scan A 88a38a96b66d
audit-deps is a command published in the GitHub repository Sagargupta16/claude-skills (5 stars, last pushed 6d ago), licensed MIT. It adds 12 tokens to every session and 220 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 commands, from other repositories
commit
Create a git commit with intelligent message drafting (-f for fast, -v for verbose).
review-arch
Review app architecture: components, data flows, risks, and prioritized improvements.
verify
Run the repo's verification loop on the current change and report real output - stage 4A of the SDLC loop.
clean-gone
Clean up local branches that have been deleted from the remote repository.
commit-push-pr
Complete workflow — commit, push, and create a pull request in one step.
checklist
Generate a custom checklist for the current feature based on user requirements.