Borrowing it
Nothing to install: this file belongs to arvindand/maven-tools-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/arvindand/maven-tools-mcp/main/.github/prompts/security-scan.prompt.mdgit clone --depth 1 https://github.com/arvindand/maven-tools-mcpWrote 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/commands/arvindand/maven-tools-mcp/security-scan)<a href="https://agentmods.dev/commands/arvindand/maven-tools-mcp/security-scan"><img src="https://agentmods.dev/badge/commands/arvindand/maven-tools-mcp/security-scan/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/commands/arvindand/maven-tools-mcp/security-scan"><img src="https://agentmods.dev/badge/commands/arvindand/maven-tools-mcp/security-scan.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.00016 | $0.00371 |
| Opus 5.5 | $0.00006 | $0.00148 |
| Sonnet 5.5 | $0.00003 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
Security Vulnerability Scan 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 1mo 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
Security Vulnerability Scan
Scan project dependencies for known security vulnerabilities using maven-tools-mcp.
Instructions
-
Extract Dependencies
- Parse the project's build file for all dependencies with versions
- Include both direct and managed dependencies if possible
-
Run Security Scan
- Use
compare_dependency_versionswithincludeSecurityScan=trueandstabilityFilter=STABLE_ONLY - Or use
analyze_project_healthwithincludeSecurityScan=truefor bulk analysis
- Use
-
Analyze Results
- Review SecuritySummary in the response
- Check for CRITICAL, HIGH, MEDIUM, LOW severity vulnerabilities
- Note which dependencies have known CVEs
Report Format
Vulnerability Summary
| Severity | Count |
|---|---|
| Critical | X |
| High | X |
| Medium | X |
| Low | X |
Affected Dependencies
For each vulnerable dependency, list:
- Dependency coordinate and current version
- CVE identifiers
- Severity and CVSS score
- Fixed version (if available)
- Recommended action
Remediation Plan
- Immediate (Critical/High): Upgrade these first
- Soon (Medium): Plan for next release
- Monitor (Low): Track but lower priority
When the newest stable version is a major upgrade but same_major_stable_fallback exists, prefer the fallback as the immediate remediation target and keep the major upgrade as a separate planned change.
Next Steps
- Generate upgrade commands for your build tool
- Test upgrades in development environment
- Review breaking changes for major version bumps
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.
- 1mo ago First seen · 59 lines · 16 tokens per session scan A 6e902c061f4b
Security Vulnerability Scan is a command published in the GitHub repository arvindand/maven-tools-mcp (35 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 371 once invoked, about $0.0001 per session on Opus 5.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-07.
Other commands, from other repositories
profile
Coordinate a reproducible Java profiling and optimization lifecycle.
type-coverage
Vérification Couverture des Types Python.
scaffold-spring-api
Scaffold a new Spring Boot 3.5.x WebFlux REST API project with standard structure, build config, and sample endpoint.
java-exercise-pattern
A command for creating a new exercise about software design patterns or SOLID principles. SOLID is a group of principles for structuring object-oriented code.
java-exercise-fix
A code-fixing command for a Java exercise that explains the correction and adds a memory aid.
checklist
Generate a custom checklist for the current feature based on user requirements.