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/ekakit/lightfast-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/rules/ekakit/lightfast-mcp/security-guidelines)<a href="https://agentmods.dev/rules/ekakit/lightfast-mcp/security-guidelines"><img src="https://agentmods.dev/badge/rules/ekakit/lightfast-mcp/security-guidelines/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/rules/ekakit/lightfast-mcp/security-guidelines"><img src="https://agentmods.dev/badge/rules/ekakit/lightfast-mcp/security-guidelines.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.00426 | $0.00426 |
| Opus 5.5 | $0.00170 | $0.00170 |
| Sonnet 5.5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
security-guidelines 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 2mo 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Guidelines
Input Validation
- Always validate inputs from AI models before processing
- Sanitize file paths to prevent directory traversal attacks
- Validate command parameters before executing system operations
- Check parameter types and ranges according to tool specifications
File System Operations
- Use appropriate permissions for file operations
- Restrict file access to designated directories only
- Validate file extensions and MIME types when applicable
- Never execute user-provided file paths directly
System Operations
- Be cautious with system-level operations that could affect the host
- Use subprocess safely with proper argument validation
- Limit resource usage to prevent DoS attacks
- Implement timeouts for long-running operations
Network Security
- Validate network endpoints before making connections
- Use secure protocols when possible (HTTPS, secure WebSocket)
- Implement rate limiting for resource-intensive operations
- Log security-relevant operations for audit trails
Error Handling
- Don't expose sensitive information in error messages
- Use generic error messages for security-sensitive failures
- Log detailed errors securely without exposing them to clients
- Handle exceptions gracefully to prevent information leakage
Example Secure Tool Implementation
@mcp.tool()
async def secure_file_operation(filepath: str) -> str:
"""Securely operate on files with validation."""
# Validate input
if not filepath or not isinstance(filepath, str):
raise ValueError("Invalid filepath provided")
# Sanitize path
safe_path = Path(filepath).resolve()
allowed_dir = Path("/allowed/directory").resolve()
# Check if path is within allowed directory
if not str(safe_path).startswith(str(allowed_dir)):
raise ValueError("Access denied: path outside allowed directory")
# Proceed with secure operation
return "Operation completed safely"
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.
- 2mo ago First seen · 58 lines · 426 tokens per session scan A 32c3d3981c7b
security-guidelines is a cursor rule published in the GitHub repository ekakit/lightfast-mcp (2 stars, last pushed 1y ago), licensed MIT. It adds 426 tokens to every session, about $0.0017 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 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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.