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 kirich1409/krozov-ai-tools --skill audit-project-dependenciesgit clone --depth 1 https://github.com/kirich1409/krozov-ai-toolsWrote 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/kirich1409/krozov-ai-tools/audit-project-dependencies)<a href="https://agentmods.dev/skills/kirich1409/krozov-ai-tools/audit-project-dependencies"><img src="https://agentmods.dev/badge/skills/kirich1409/krozov-ai-tools/audit-project-dependencies/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/kirich1409/krozov-ai-tools/audit-project-dependencies"><img src="https://agentmods.dev/badge/skills/kirich1409/krozov-ai-tools/audit-project-dependencies.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00080 | $0.00658 |
| Opus 5 | $0.00040 | $0.00329 |
| Sonnet 5 | $0.00016 | $0.00132 |
| Haiku 4.5 | $0.00008 | $0.00066 |
Grade A, and why
audit-project-dependencies 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 10d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Project Dependencies
Run one combined dependency audit: scan the project, check for available updates,
optionally query OSV.dev for vulnerabilities, and optionally add license categorization —
in a single tool call instead of chaining /scan-project-dependencies +
/compare-dependency-versions + /dependency-vulnerabilities + /dependency-license by
hand.
Steps
-
Call
audit_project_dependencieswith:projectPath(default: cwd)includeVulnerabilities— defaulttrueproductionOnly— defaulttrue(excludes test-scope dependencies)includeLicenses— defaultfalse; settruewhen the user wants license posture in the same report (adds extra POM/GitHub fetches, so it's opt-in)
-
Present the report:
- Upgrade table from
dependencies[](current → latest,upgradeType), grouped bysource.kindlike/check-depsdoes. - Vulnerabilities section for any entry with non-empty
vulnerabilities[], sorted by severity; call outmalicious: truefindings first. - When
includeLicenseswas set, alicensessection (summary.byCategory,uniqueSpdxIds,hasProprietaryOrCopyleft) plusnewLicenseCategories— categories that appear exactly once in the scanned set (e.g. one AGPL dependency in an otherwise Apache/MIT tree). - Lead with the
summaryblock (total,upgradeable,vulnerable,major,minor,patch) as the headline, details below.
- Upgrade table from
-
Follow the same confirm-before-edit discipline as
/check-depsif the user wants updates applied — this skill's job is the combined report, not unattended edits.
Constraints and non-goals
- Not for only checking for updates —
/check-depsis narrower and offers to apply them. - Not for only checking vulnerabilities against a whole project —
/check-deps-vulnerabilities. - Not for a single named dependency outside project context —
/check-multiple-versions,/compare-dependency-versions,/dependency-vulnerabilities, or/dependency-license.
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.
- 10d ago First seen · 58 lines · 80 tokens per session scan A 883b42426f26
audit-project-dependencies is a skill published in the GitHub repository kirich1409/krozov-ai-tools (22 stars, last pushed 5d ago), licensed MIT. It adds 80 tokens to every session and 658 once invoked, about $0.0004 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-09-01.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.