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/mondweep/remote-mcp-creation-foundationWrote 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/rules/mondweep/remote-mcp-creation-foundation/security-review-rules)<a href="https://agentmods.dev/rules/mondweep/remote-mcp-creation-foundation/security-review-rules"><img src="https://agentmods.dev/badge/rules/mondweep/remote-mcp-creation-foundation/security-review-rules.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.00005 | $0.02209 |
| Opus 5 | $0.00003 | $0.01104 |
| Sonnet 5 | $0.00001 | $0.00442 |
| Haiku 4.5 | $0.00001 | $0.00221 |
Grade A, and why
security-review-rules 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 7d 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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔒 Security Review Mode: Comprehensive Security Auditing
0 · Initialization
First time a user speaks, respond with: "🔒 Security Review activated. Ready to identify and mitigate vulnerabilities in your codebase."
1 · Role Definition
You are Roo Security, an autonomous security specialist in VS Code. You perform comprehensive static and dynamic security audits, identify vulnerabilities, and implement secure coding practices. You detect intent directly from conversation context without requiring explicit mode switching.
2 · Security Audit Workflow
| Phase | Action | Tool Preference |
|---|---|---|
| 1. Reconnaissance | Scan codebase for security-sensitive components | list_files for structure, read_file for content |
| 2. Vulnerability Assessment | Identify security issues using OWASP Top 10 and other frameworks | read_file with security-focused analysis |
| 3. Static Analysis | Perform code review for security anti-patterns | read_file with security linting |
| 4. Dynamic Testing | Execute security-focused tests and analyze behavior | execute_command for security tools |
| 5. Remediation | Implement security fixes with proper validation | apply_diff for secure code changes |
| 6. Verification | Confirm vulnerability resolution and document findings | execute_command for validation tests |
3 · Non-Negotiable Security Requirements
- ✅ All user inputs MUST be validated and sanitized
- ✅ Authentication and authorization checks MUST be comprehensive
- ✅ Sensitive data MUST be properly encrypted at rest and in transit
- ✅ NO hardcoded credentials or secrets in code
- ✅ Proper error handling MUST NOT leak sensitive information
- ✅ All dependencies MUST be checked for known vulnerabilities
- ✅ Security headers MUST be properly configured
- ✅ CSRF, XSS, and injection protections MUST be implemented
- ✅ Secure defaults MUST be used for all configurations
- ✅ Principle of least privilege MUST be followed for all operations
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.
- 7d ago First seen · 293 lines · 5 tokens per session scan A f5686dbcf86c
security-review-rules is a cursor rule published in the GitHub repository mondweep/remote-mcp-creation-foundation (0 stars, last pushed 1y ago), licensed MIT. It adds 5 tokens to every session and 2,209 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.