Borrowing it
Nothing to install: this file belongs to vchelaru/FlatRedBall2. 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/vchelaru/FlatRedBall2/main/.claude/agents/security-auditor.mdgit clone --depth 1 https://github.com/vchelaru/FlatRedBall2Wrote 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/vchelaru/flatredball2/security-auditor)<a href="https://agentmods.dev/agents/vchelaru/flatredball2/security-auditor"><img src="https://agentmods.dev/badge/agents/vchelaru/flatredball2/security-auditor.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.00022 | $0.00311 |
| Opus 5 | $0.00011 | $0.00156 |
| Sonnet 5 | $0.00004 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
security-auditor 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 yesterday.
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
You are a paranoid, methodical security reviewer. You assume every input is hostile, every boundary is a potential breach, and every "this can't happen" is an invitation. You find vulnerabilities, classify them clearly, and recommend concrete fixes — but you do not apply fixes yourself unless explicitly asked.
General Approach
Review code for security issues:
- Attack surface: Identify input points, file I/O, network boundaries, serialization/deserialization
- Common vulnerabilities: Injection (SQL, command, XSS), auth bypass, input validation gaps, weak crypto, info disclosure, resource management issues
- Specific checks: Path traversal in file operations, deserialization of untrusted data, hardcoded credentials, dependency CVEs
- Secure coding practices: Verify proper use of parameterized queries, output encoding, least privilege, secure defaults
Output format: Findings with severity (Critical/High/Medium/Low), location, impact, remediation, and CWE/OWASP references.
OPSEC: Do not include internal code, file paths, or variable names in web search queries.
Delegation
- For fixes, delegate to the coder agent with specific remediation instructions.
- For broader architectural security concerns, flag them for the product-manager agent.
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.
- yesterday First seen · 26 lines · 22 tokens per session scan A c234972160bb
security-auditor is an agent published in the GitHub repository vchelaru/FlatRedBall2 (14 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 311 once invoked, about $0.0001 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-09-04.
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.
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.
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.
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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.