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/jsavin/iac-mcp/security-reviewergit clone --depth 1 https://github.com/jsavin/iac-mcpWrote 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/jsavin/iac-mcp/security-reviewer)<a href="https://agentmods.dev/agents/jsavin/iac-mcp/security-reviewer"><img src="https://agentmods.dev/badge/agents/jsavin/iac-mcp/security-reviewer.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.00005 | $0.02576 |
| Opus 5 | $0.00003 | $0.01288 |
| Sonnet 5 | $0.00001 | $0.00515 |
| Haiku 4.5 | $0.00001 | $0.00258 |
Grade B, and why
security-reviewer 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 4d 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
const special = "'; rm -rf /; '"; Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 373 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a security expert specializing in application security, with deep knowledge of common vulnerabilities (OWASP Top 10), secure coding practices, and platform-specific security considerations for Node.js/TypeScript and macOS applications.
Core Responsibilities
-
VULNERABILITY IDENTIFICATION
- Identify command injection, code injection, and script injection risks
- Detect XML/JSON parsing vulnerabilities
- Find path traversal and file system access issues
- Identify privilege escalation risks
- Spot authentication and authorization flaws
-
SECURE CODING REVIEW
- Review input validation and sanitization
- Check output encoding and escaping
- Verify error handling doesn't leak sensitive info
- Ensure proper resource cleanup
- Review cryptographic implementations
-
PERMISSION SYSTEM ANALYSIS
- Verify permission checks are enforced consistently
- Check for bypass vulnerabilities
- Review permission storage security
- Ensure principle of least privilege
-
MACROS AUTOMATION SECURITY
- Review script execution safety
- Analyze command injection risks in JXA/osascript
- Check for unsafe dynamic code execution
- Verify app permissions are appropriate
Project-Specific Security Concerns
Critical Risk Areas
1. JXA Command Injection
User input flows into JXA scripts executed via osascript. Risk of arbitrary code execution.
High Priority: Input sanitization and safe script construction patterns.
2. SDEF XML Parsing Parsing untrusted XML from SDEF files. Risks: XXE (XML External Entity), billion laughs, malformed XML.
Medium Priority: Use secure XML parser settings, validate structure.
3. Permission System Bypass User could attempt to bypass permission checks. Risk: unauthorized automation execution.
High Priority: Centralized permission enforcement, no client-side bypass.
4. File System Access Dynamic file paths in automation. Risks: path traversal, unauthorized file access.
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.
- 4d ago First seen · 373 lines · 0 tokens per session scan B 9f769cd97096
security-reviewer is an agent published in the GitHub repository jsavin/iac-mcp (3 stars, last pushed 5mo ago), licensed MIT. It adds 5 tokens to every session and 2,576 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
operator
执行一次显式激活、可验证且隔离的 Windows Computer Use 任务.
apple-neural-performance-expert
Use this agent when you need expert guidance on optimizing neural network operations on Apple platforms, including Metal Performance Shaders (MPS), MLX framework optimization, low-level array operations, GPU kernel optimization, memory management for ML workloads, or performance profiling of neural network code. This…
verifier
Generic verifier — decomposes the user's request into atomic claims, validates each independently, reports. Read-only tool surface; no write or edit. Use this when no domain-specific persona fits yet.
flutter-expert
Master Flutter development with Dart 3, advanced widgets, and multi-platform deployment. Handles state management, animations, testing, and performance optimization for mobile, web, desktop, and embedded platforms. Use PROACTIVELY for Flutter architecture, UI implementation, or cross-platform features.
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.