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 Qualimetry/claude-code-qualimetry-ai-app --skill dependency-checkgit clone --depth 1 https://github.com/Qualimetry/claude-code-qualimetry-ai-appWrote 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/qualimetry/claude-code-qualimetry-ai-app/dependency-check)<a href="https://agentmods.dev/skills/qualimetry/claude-code-qualimetry-ai-app/dependency-check"><img src="https://agentmods.dev/badge/skills/qualimetry/claude-code-qualimetry-ai-app/dependency-check/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/qualimetry/claude-code-qualimetry-ai-app/dependency-check"><img src="https://agentmods.dev/badge/skills/qualimetry/claude-code-qualimetry-ai-app/dependency-check.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.00099 | $0.02197 |
| Opus 5 | $0.00049 | $0.01099 |
| Sonnet 5 | $0.00020 | $0.00439 |
| Haiku 4.5 | $0.00010 | $0.00220 |
Grade A, and why
dependency-check 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 4d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Vulnerability Resolution
When invoked, follow this four-phase workflow to identify and clear dependency CVE vulnerabilities for the current repository branch.
Phase 1: Assess
Gather repository context and fetch the vulnerability report with inline upgrade advice.
- Determine the
repositoryNameandbranchName:
repositoryName — the repository name in owner/repo-name format (e.g., organisation/my-project). The server is case-insensitive and handles .git suffixes automatically.
analysisName (optional) — if the repository is a mono-repo with multiple analysis projects, provide the analysis project name to disambiguate. Case-insensitive. Leave empty for single-project repositories.
branchName — run this shell command:
git branch --show-current
This returns the branchName.
-
Call
get_dependency_vulnerabilitieswithrepositoryName,branchName, and optionallyanalysisName. The response includes inline upgrade advice for each dependency:NextSafeVersion,LatestVersion,UpgradeRisk, andCurrentVersionIsDeprecated.Two optional filters are available:
cve- narrow the whole response to a single CVE (e.g.CVE-2020-28500) across every dependency. Use it when the user asks about one advisory.includeSuppressed- defaultfalse. Set it totrueto also list, per dependency, the CVEs an approved suppression has already removed, each with its scope, requester, reason and expiry. Use it when the user asks what has been accepted, or when a CVE they expected to see is missing.
-
Check the suppression flags before planning any work. See Suppressions below.
- A CVE with
SuppressionPendingis waiting for someone to approve a suppression for it. Report it, do not spend effort fixing it, and move on. - A dependency with
SuppressionExpiringSoonhas an approved suppression that runs out within 15 days. The findings it hides today will reappear when it does, so raise it with the user now.
- A CVE with
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago Changed · +36 lines · +21 tokens per session df5fc3a90fae
- 9d ago First seen · 129 lines · 78 tokens per session scan A c96ed6605949
dependency-check is a skill published in the GitHub repository Qualimetry/claude-code-qualimetry-ai-app (1 stars, last pushed 4d ago), licensed Apache-2.0. It adds 99 tokens to every session and 2,197 once invoked, about $0.0005 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
improve-code-quality
Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy…
refactoring-patterns
Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", "decompose conditional", or "clean up this messy code". Also trigger when…
team-review
Review changed code for reuse, quality, and efficiency using a team of persistent named reviewers. This skill should be used when the user says "team review", "review with team", or wants parallel code review with persistent team members for follow-up questions. Similar to /subagent-review but reviewers persist after…
roslyn-query
Query .NET/C# codebases using Roslyn AST analysis via dotnet run file. Use for tracing data flow, auditing API usage, finding pattern violations, or ad-hoc codebase queries.
review-responder
Use when receiving feedback on code you implemented, responding to reviewer comments, deciding which review suggestions to implement, or pushing back on incorrect review feedback.
codex
Route a task to OpenAI's Codex CLI (codex exec) instead of doing it yourself. Use this skill ANY time the user names codex or types /codex — even for routine work Claude could handle, because the user is choosing to delegate. The intent: 'ask codex', 'have codex review/refactor this', 'check/validate with codex', 'see…