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/check-depsgit 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/check-deps)<a href="https://agentmods.dev/commands/harish-garg/security-scanner-plugin/check-deps"><img src="https://agentmods.dev/badge/commands/harish-garg/security-scanner-plugin/check-deps.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.1 | $0.00008 | $0.00471 |
| Opus 5 | $0.00004 | $0.00235 |
| Sonnet 5 | $0.00002 | $0.00094 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
check-deps 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 5d 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 Dependencies
Quickly scan for dependency vulnerabilities in the current repository.
What to do:
-
Identify repository: Determine the current repository (owner/repo) from Git configuration
- Use
git remote -vor check.git/configto find the repository - Parse owner and repo name from GitHub URL
- Use
-
Scan for vulnerabilities: Use GitHub MCP's
list_dependabot_alertstool with parameters:owner: repository ownerrepo: repository namestate: "open" (to show only unresolved issues)
-
Analyze and summarize results:
- Count total vulnerable dependencies
- Group by severity level (critical, high, medium, low)
- Sort by severity (critical first)
-
Present concise summary:
Dependency Scan Results for owner/repo Total vulnerabilities: X - Critical: X - High: X - Medium: X - Low: X 🔴 Critical & High Priority: 1. package-name@version - CVE-XXXX-XXXX (Critical) Impact: [Brief description] Fix: Upgrade to version X.X.X 2. another-package@version - CVE-XXXX-XXXX (High) Impact: [Brief description] Fix: Upgrade to version X.X.X [List up to 5 most critical issues] 💡 Next steps: - Run /explain-cve CVE-XXXX-XXXX for details on specific vulnerabilities - Run /security-scan for comprehensive audit including code and secrets - Review all X open alerts on GitHub: https://github.com/owner/repo/security -
Handle edge cases:
- If no repository found: "Unable to detect repository. Ensure you're in a Git directory linked to GitHub."
- If no vulnerabilities: "✅ No dependency vulnerabilities found! Your dependencies are up to date."
- If GitHub MCP not configured: "GitHub MCP Server not found. Please configure it first."
Keep the output concise and actionable. Focus on what needs immediate attention.
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.
- 5d ago First seen · 57 lines · 8 tokens per session scan A 133e6ad26546
check-deps is a command published in the GitHub repository harish-garg/security-scanner-plugin (9 stars, last pushed 11mo ago), licensed MIT. It adds 8 tokens to every session and 471 once invoked, about $0.0000 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 commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.