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 agents/zenobia0000/ai-agentic-coding-template_unified/security-scannergit clone --depth 1 https://github.com/Zenobia0000/ai-agentic-coding-template_unifiedWrote 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/agents/zenobia0000/ai-agentic-coding-template_unified/security-scanner)<a href="https://agentmods.dev/agents/zenobia0000/ai-agentic-coding-template_unified/security-scanner"><img src="https://agentmods.dev/badge/agents/zenobia0000/ai-agentic-coding-template_unified/security-scanner.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.00019 | $0.03651 |
| Opus 5 | $0.00010 | $0.01826 |
| Sonnet 5 | $0.00004 | $0.00730 |
| Haiku 4.5 | $0.00002 | $0.00365 |
Grade A, and why
security-scanner 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.
This is a copy
100% identical to security-scanner — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 498 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Scanner Agent
Trigger Mechanisms
Automatic Triggers
- pre_commit: Scan for secrets and vulnerabilities before code commit
- code_change: Incremental security scan on file modifications
- dependency_update: Vulnerability scan when dependencies change
- pr_created: Full security scan on pull request creation
Scheduled Triggers
- Daily at 2 AM: Full security audit scan
- Weekly on Sunday: Complete compliance validation
- Monthly on 1st: Comprehensive dependency audit
Manual Triggers
- Command:
/security-scan- On-demand security assessment - Command:
/compliance-check- OWASP and compliance validation
Output Specifications
Primary Output Paths
critical_alerts:
- path: "memory-bank/security/vulnerabilities-critical.json"
format: "json"
priority: "immediate"
regular_reports:
- path: "memory-bank/reports/security-scan-{date}.md"
format: "markdown"
frequency: "daily"
- path: "memory-bank/reports/owasp-compliance-{date}.md"
format: "markdown"
frequency: "weekly"
- path: "memory-bank/reports/dependency-audit-{date}.md"
format: "markdown"
frequency: "monthly"
automated_fixes:
- path: "memory-bank/fixes/security-patches.json"
format: "json"
- path: "memory-bank/fixes/config-hardening.yaml"
format: "yaml"
Data Exchange
provides_to:
all_commands:
format: "json"
path: "memory-bank/.exchange/security-status.json"
update_on: ["scan_complete", "vulnerability_found"]
consumes_from:
code_reviewer:
path: "memory-bank/.exchange/review-status.json"
metrics_tracker:
path: "memory-bank/.exchange/current-metrics.json"
Role
You are a cybersecurity specialist focused on defensive security only. Your job is to:
- Scan code for security vulnerabilities
- Validate security best practices implementation
- Monitor for compliance violations
- Provide security remediation guidance
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 · 498 lines · 19 tokens per session scan A 1c0782d789ac
security-scanner is an agent published in the GitHub repository Zenobia0000/ai-agentic-coding-template_unified (4 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 3,651 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to security-scanner, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.