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 commands/harish-garg/security-scanner-plugin/explain-cvegit clone --depth 1 https://github.com/harish-garg/security-scanner-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/commands/harish-garg/security-scanner-plugin/explain-cve)<a href="https://agentmods.dev/commands/harish-garg/security-scanner-plugin/explain-cve"><img src="https://agentmods.dev/badge/commands/harish-garg/security-scanner-plugin/explain-cve.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.00010 | $0.00591 |
| Opus 5 | $0.00005 | $0.00296 |
| Sonnet 5 | $0.00002 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade B, and why
explain-cve scanned grade B with 1 finding 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
This vulnerability allows attackers to inject and execute arbitrary commands How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explain CVE
Help users understand what a specific vulnerability means and how to fix it.
Usage
This command can be used in two ways:
- With CVE argument:
/explain-cve CVE-2021-23337 - Interactive:
/explain-cve(will prompt for CVE)
What to do:
-
Extract CVE from arguments: Check if user provided CVE/vulnerability ID after the command
- If provided, use that CVE identifier directly
- If not provided, ask for the CVE identifier or vulnerability name
-
Identify repository context: Determine the current repository (owner/repo) from the working directory
-
Gather information:
- Use GitHub MCP's
list_dependabot_alertsto check if this CVE affects the current repo - If found, use
get_dependabot_alertto get detailed information - If not found in current repo, provide general CVE information
- Use GitHub MCP's
-
Explain in plain English:
- What it is: Brief description of the vulnerability type (e.g., "SQL Injection", "Command Injection")
- Impact: What could happen if exploited (e.g., "Remote Code Execution", "Data Exposure")
- Affected versions: Which package versions are vulnerable
- Fixed versions: Which versions include the fix
- How to fix: Specific upgrade commands and steps
- Workarounds: Temporary mitigations if upgrade isn't immediately possible
- Risk level: Severity rating with context for this specific project
Example Output Format
CVE-2021-23337 - Command Injection in lodash
What it is:
This vulnerability allows attackers to inject and execute arbitrary commands
through lodash template strings. The issue occurs when user-controlled input
is processed by lodash's template function without proper sanitization.
Impact: 🔴 Critical - Remote Code Execution
Attackers can execute arbitrary code on your server if your application
processes user input through lodash templates.
Affected versions: lodash < 4.17.21
Fixed in: lodash 4.17.21 and later
How to fix:
npm install lodash@latest
or
yarn upgrade lodash@^4.17.21
Workaround (if immediate upgrade not possible):
Avoid using lodash template() with user-controlled input, or implement
strict input validation before processing.
Status in this repository:
✅ Not affected - you're using [email protected]
OR
⚠️ Vulnerable - found in package.json ([email protected])
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 · 70 lines · 10 tokens per session scan B 1cc8ff243492
explain-cve is a command published in the GitHub repository harish-garg/security-scanner-plugin (9 stars, last pushed 10mo ago), licensed MIT. It adds 10 tokens to every session and 591 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.