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 skills/sonatype/sonatype-cursor-plugin/check-dependencynpx skills add sonatype/sonatype-cursor-plugin --skill check-dependencygit clone --depth 1 https://github.com/sonatype/sonatype-cursor-pluginWrote 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/sonatype/sonatype-cursor-plugin/check-dependency)<a href="https://agentmods.dev/skills/sonatype/sonatype-cursor-plugin/check-dependency"><img src="https://agentmods.dev/badge/skills/sonatype/sonatype-cursor-plugin/check-dependency.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 | $0.00040 | $0.00505 |
| Opus 5 | $0.00020 | $0.00253 |
| Sonnet 5 | $0.00008 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
check-dependency 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 3d 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
Check dependency
Trigger
Use when you need to evaluate a specific dependency's security, license, and quality posture.
Required Inputs
- Package identifier (one of):
- Package name and version (e.g.,
lodash 4.17.21) - PURL format (e.g.,
pkg:npm/[email protected]) - Maven coordinates (e.g.,
org.apache.commons:commons-lang3:3.12.0)
- Package name and version (e.g.,
Workflow
- Parse the dependency identifier from user input or current file context.
- Convert to PURL format if needed:
- npm:
pkg:npm/<name>@<version> - Maven:
pkg:maven/<groupId>/<artifactId>@<version> - PyPI:
pkg:pypi/<name>@<version> - Go:
pkg:golang/<module>@<version>
- npm:
- Call
getComponentVersionMCP tool with the PURL. - Present findings in a structured format:
- Security: Known vulnerabilities (CVEs) with severity
- License: License type and compatibility concerns
- Quality: Maintainability and reliability metrics
- Developer Trust Score: Overall recommendation score
- If issues found, suggest alternatives using
/find-safer-version.
Output
- Component analysis summary
- Risk assessment (Critical/High/Medium/Low/None)
- Actionable recommendations
- Link to detailed Sonatype Guide report
Example
User: Check lodash 4.17.20
Response:
## lodash 4.17.20 Analysis
**Risk Level**: High
### Security
- CVE-2021-23337 (High): Prototype pollution in lodash
- CVE-2020-8203 (High): Prototype pollution via zipObjectDeep
### License
- MIT License - permissive, commercial-friendly
### Quality
- Developer Trust Score: 72/100
- Last updated: 2 years ago
### Recommendation
Upgrade to lodash 4.17.21 which addresses these vulnerabilities.
Run `/find-safer-version lodash` for detailed upgrade options.
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.
- 3d ago First seen · 67 lines · 40 tokens per session scan A 4e6d9f3d9e0e
check-dependency is a skill published in the GitHub repository sonatype/sonatype-cursor-plugin (0 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 505 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…