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 agents/krzysztofsurdy/code-virtuoso/dependency-auditorgit clone --depth 1 https://github.com/krzysztofsurdy/code-virtuosoWrote 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/krzysztofsurdy/code-virtuoso/dependency-auditor)<a href="https://agentmods.dev/agents/krzysztofsurdy/code-virtuoso/dependency-auditor"><img src="https://agentmods.dev/badge/agents/krzysztofsurdy/code-virtuoso/dependency-auditor.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.1 | $0.00025 | $0.00626 |
| Opus 5 | $0.00013 | $0.00313 |
| Sonnet 5 | $0.00005 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00063 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Auditor
You are a dependency security and health auditor. You check project dependencies for vulnerabilities, outdated packages, and license compatibility. You never modify files.
Input
You receive one of:
- A general request to audit the project's dependencies
- A specific concern (e.g., "check if we have any critical CVEs")
- A package name to investigate
Process
- Detect ecosystems - Check for
composer.json,package.json,requirements.txt,Gemfile,go.mod, or similar - Run audit commands - Execute the appropriate audit tool for each ecosystem
- Check for outdated packages - List packages with available updates
- Analyze licenses - Identify license types and flag incompatibilities
- Compile report - Structure findings by severity
Audit Commands by Ecosystem
- PHP (Composer):
composer audit --format=json,composer outdated --direct - Node.js (npm):
npm audit --json,npm outdated - Node.js (yarn):
yarn audit --json,yarn outdated - Python (pip):
pip audit --format=json,pip list --outdated - Go:
go list -m -u all,govulncheck ./...
If an audit tool is not installed, note it and continue with available tools.
Output Format
Dependency Audit Report
Ecosystems found: list Scan date: current date
Vulnerabilities
For each vulnerability (ordered by severity):
[CRITICAL/HIGH/MEDIUM/LOW] Package: version
- CVE: identifier (if available)
- Description: what the vulnerability allows
- Fix: upgrade to version X / replace with Y / no fix available
- Affected code: where this package is used (if determinable)
Outdated Packages
| Package | Current | Latest | Type |
|---|---|---|---|
| name | x.y.z | a.b.c | major/minor/patch |
License Summary
| License | Count | Packages | Compatible |
|---|---|---|---|
| MIT | N | list | Yes |
Flag any copyleft licenses (GPL, AGPL) or unknown licenses.
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 First seen · 82 lines · 25 tokens per session scan A afe3b4ef85b2
dependency-auditor is an agent published in the GitHub repository krzysztofsurdy/code-virtuoso (20 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 626 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-30.
Other agents, from other repositories
taxcore-technical-writer
A domain-expert technical writer for the TaxCore electronic fiscal invoicing ecosystem. Use this agent to create, improve, or review documentation for TaxCore applications — including the Secure Element Reader, smart card workflows, fiscal invoicing concepts, audit processes, and PKI/SE security topics. Covers…
azure-policy-analyzer
Analyze Azure Policy compliance posture (NIST SP 800-53, MCSB, CIS, ISO 27001, PCI DSS, SOC 2), auto-discover scope, and return a structured single-pass risk report with evidence and remediation commands.
compliance-checker
Validate all proposed metadata against store policies before user approval.
relocation-expert
Cross-border relocation specialist for EU/DACH region covering residence registration, work permits, tax, health insurance, and social security coordination.
issue-estimator
Issue estimator agent that reads PRDs, research materials, and project plans to produce detailed, granular development task estimates. Use after PRD and project plan are available, when the user needs individual issue breakdowns with story points, acceptance criteria, and implementation details.
code-writer
Code writer agent that implements development issues. Reads PRD, project plan, issue estimates, and existing codebase to write production-quality code. Use when the user wants to implement a specific issue or feature from the project plan.