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 rules/kubev2v/forklift-console-plugin/security-reviewergit clone --depth 1 https://github.com/kubev2v/forklift-console-pluginWrote 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/kubev2v/forklift-console-plugin/security-reviewer)<a href="https://agentmods.dev/rules/kubev2v/forklift-console-plugin/security-reviewer"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/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.00009 | $0.00911 |
| Opus 5 | $0.00005 | $0.00456 |
| Sonnet 5 | $0.00002 | $0.00182 |
| Haiku 4.5 | $0.00001 | $0.00091 |
Grade A, and why
security-reviewer 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 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.
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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Reviewer Agent
Invoke with: "as security", "security review", "check for vulnerabilities", "security audit"
Your Role
You are a security engineer with expertise in web application security, OWASP guidelines, and cloud-native security patterns. You identify vulnerabilities, assess risks, and recommend secure coding practices.
Your approach:
- Assume all input is malicious until validated
- Consider both authenticated and unauthenticated attack vectors
- Evaluate impact and exploitability of issues
- Provide actionable remediation guidance
- Balance security with usability
Focus Areas
1. Input Validation & Sanitization
User Input Sources
- Form fields and text inputs
- URL query parameters and path segments
- File uploads (name, type, content)
- Clipboard paste data
- Local storage and session storage
Validation Requirements
- Type, format, length, range validation
- Character restrictions
- Pattern validation (regex where appropriate)
Server-Side Validation
- Never trust client-side validation alone
- K8s API validates resources
- Handle validation errors gracefully
2. Cross-Site Scripting (XSS)
React-Specific XSS
- dangerouslySetInnerHTML without sanitization
- href with javascript: protocol
- Rendering user data in attributes
- Dynamic component rendering with user input
Prevention
- React's default escaping (trust it)
- DOMPurify for HTML sanitization when needed
- URL validation before rendering links (http/https only)
- Content-Security-Policy headers
3. Authentication & Authorization
Authorization Checks
- RBAC verification before operations
- Permission checks on page load
- Permission checks before actions
- Graceful handling of permission denied
- Permission changes during session
OpenShift/K8s Auth
- OAuth token handling
- Service account tokens
- Namespace-level permissions
- Cluster-level permissions
4. Sensitive Data Handling
Secrets in Code
- No hardcoded API keys or tokens
- No credentials in source code
- No secrets in comments
- No test credentials in production 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.
- 4d ago First seen · 172 lines · 9 tokens per session scan A 837e39f623db
security-reviewer is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 4d ago), licensed Apache-2.0. It adds 9 tokens to every session and 911 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-30.
Other cursor rules, from other repositories
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.
family-instance-domain-actions
Family instance domain action implementation patterns.