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 GktuOktay/ai-skills --skill dependency-auditgit clone --depth 1 https://github.com/GktuOktay/ai-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/gktuoktay/ai-skills/dependency-audit)<a href="https://agentmods.dev/skills/gktuoktay/ai-skills/dependency-audit"><img src="https://agentmods.dev/badge/skills/gktuoktay/ai-skills/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/gktuoktay/ai-skills/dependency-audit"><img src="https://agentmods.dev/badge/skills/gktuoktay/ai-skills/dependency-audit.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.00064 | $0.00737 |
| Opus 5 | $0.00032 | $0.00368 |
| Sonnet 5 | $0.00013 | $0.00147 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
Software Composition and Dependency Auditing 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 11d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software Composition & Dependency Auditing
Overview
This skill focuses on managing the security of third-party libraries and tools used in your project. It covers Software Composition Analysis (SCA), auditing dependencies, handling Common Vulnerabilities and Exposures (CVEs), preventing lockfile poisoning, and establishing automated update strategies.
Core Principles
1. Software Composition Analysis (SCA)
Understand what comprises your application.
- Inventory: Maintain an accurate inventory of all direct and transitive dependencies (e.g., SBOM - Software Bill of Materials).
- Continuous Monitoring: Regularly scan your dependency tree for known vulnerabilities.
2. Auditing Dependencies
Ensure that libraries pulled from package managers (npm, pip, Maven, etc.) are safe.
- Run audits regularly: Use built-in tools like
npm audit,pip-audit, or third-party tools like Snyk or OWASP Dependency-Check in your CI/CD pipeline. - Assess risk: Evaluate the severity of CVEs. A high-severity vulnerability in a dev dependency might pose a lower risk than a medium-severity one in production code, but both should be addressed.
3. Supply Chain Security and Lockfile Poisoning
Prevent malicious packages from entering your build process.
- Lock files: Always commit your lock files (
package-lock.json,yarn.lock,Pipfile.lock,requirements.txtwith hashes) to ensure deterministic builds. - Verify integrity: Ensure package managers are configured to check integrity hashes. Watch out for unauthorized changes to lock files during PR reviews (lockfile poisoning).
- Typosquatting: Double-check package names before installation to avoid typosquatting attacks (e.g.,
electroinstead ofelectron).
4. Automated Dependency Updates
Keep dependencies up-to-date to patch vulnerabilities proactively.
- Automation tools: Use tools like Dependabot or Renovate to automatically create PRs for dependency updates.
- Testing: Ensure you have a robust automated test suite so you can confidently merge dependency updates.
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.
- 11d ago First seen · 70 lines · 64 tokens per session scan A 07d234be0f2a
Software Composition and Dependency Auditing is a skill published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 8d ago), licensed MIT. It adds 64 tokens to every session and 737 once invoked, about $0.0003 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
azure-resource-manager-mysql-dotnet
Azure MySQL Flexible Server SDK for .NET. Database management for MySQL Flexible Server deployments.
aws-security-audit
Comprehensive AWS security posture assessment using AWS CLI and security best practices.
azure-microsoft-playwright-testing-ts
Run Playwright tests at scale with cloud-hosted browsers and integrated Azure portal reporting.
gha-security-review
Find exploitable vulnerabilities in GitHub Actions workflows. Every finding MUST include a concrete exploitation scenario — if you can't build the attack, don't report it.
performance-optimizer
Identifies and fixes performance bottlenecks in code, databases, and APIs. Measures before and after to prove improvements.
azure-mgmt-apicenter-py
Azure API Center Management SDK for Python. Use for managing API inventory, metadata, and governance across your organization.