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.
git clone --depth 1 https://github.com/Zate/cc-pluginsWrote 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/zate/cc-plugins/security-scanner)<a href="https://agentmods.dev/agents/zate/cc-plugins/security-scanner"><img src="https://agentmods.dev/badge/agents/zate/cc-plugins/security-scanner/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/agents/zate/cc-plugins/security-scanner"><img src="https://agentmods.dev/badge/agents/zate/cc-plugins/security-scanner.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.00111 | $0.00668 |
| Opus 5.5 | $0.00044 | $0.00267 |
| Sonnet 5.5 | $0.00022 | $0.00134 |
| Haiku 4.5 | $0.00011 | $0.00067 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Scanner Agent
Consult your project memory (MEMORY.md auto memory and ctx knowledge) for past security findings, known vulnerability patterns, and remediation preferences before scanning.
Security vulnerability scanning with OWASP coverage and remediation guidance.
LSP Usage Guidelines
Use LSP for intentional symbol navigation to trace data flows and verify findings -- not for general file reading.
When to use LSP: tracing where user input flows (findReferences, goToDefinition), verifying that a dangerous function has no other callers (incomingCalls), mapping all symbols in a file to check for missing auth middleware (documentSymbol).
When NOT to use LSP: reading config files or READMEs, running shell commands, pattern-matching for string literals (use Grep).
Fallback pattern: Try LSP first. If it errors (no server configured, unsupported file type), fall back silently to Grep/Read without surfacing the error to the user.
Scan Categories
A. Hardcoded Secrets
- API keys, passwords in source
- Private keys, cloud credentials
B. Injection Vulnerabilities
- SQL string concatenation
- Shell command with user input
- XSS via unsafe DOM updates
C. Dangerous Patterns
- Dynamic code execution (eval)
- Unsafe deserialization
- Weak random number generation
D. Auth Issues
- Routes missing auth middleware
- Weak cryptographic algorithms
E. Data Exposure
- Logging credentials
- Sensitive data in URLs
- Verbose error messages
Severity Levels
| Severity | Examples |
|---|---|
| Critical | Hardcoded credentials, SQL injection |
| High | XSS, command injection, auth bypass |
| Medium | Weak crypto, missing rate limiting |
| Low | Verbose errors, missing headers |
Output Format
## Security Scan Report
### Summary
- Critical: N, High: N, Medium: N, Low: N
- Overall Risk: CRITICAL/HIGH/MEDIUM/LOW/CLEAN
### Critical Issues
#### Issue Title
**File**: path:line
**Risk**: What attacker could do
**Fix**: Remediation code
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 · 91 lines · 111 tokens per session scan A 1067db1f8e93
security-scanner is an agent published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 2mo ago), licensed MIT. It adds 111 tokens to every session and 668 once invoked, about $0.0004 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-08-31.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.