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/timurgaleev/vibestackWrote 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/timurgaleev/vibestack/security)<a href="https://agentmods.dev/rules/timurgaleev/vibestack/security"><img src="https://agentmods.dev/badge/rules/timurgaleev/vibestack/security/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/timurgaleev/vibestack/security"><img src="https://agentmods.dev/badge/rules/timurgaleev/vibestack/security.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.00311 | $0.00311 |
| Opus 5 | $0.00156 | $0.00156 |
| Sonnet 5 | $0.00062 | $0.00062 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
security 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
Security Guidelines
Mandatory Security Checks
Run this checklist on changes that touch a security-relevant area — authentication, authorization, cryptography, external input, secret handling, or sensitive data. It is not a per-commit ritual for unrelated work.
- No hardcoded secrets (API keys, passwords, tokens)
- All user inputs validated
- SQL injection prevention (parameterized queries)
- XSS prevention (sanitized HTML)
- CSRF protection enabled
- Authentication/authorization verified
- Rate limiting on all endpoints
- Error messages don't leak sensitive data
Secret Management
// NEVER: Hardcoded secrets
const apiKey = "sk-proj-xxxxx"
// ALWAYS: Environment variables
const apiKey = process.env.OPENAI_API_KEY
if (!apiKey) {
throw new Error('OPENAI_API_KEY not configured')
}
Confirm Before Acting
Report the blast radius and get confirmation before changing:
- Authentication, session, or token handling
- Authorization logic
- Encryption, hashing, or signing
- PII or payment data handling
- Credentials for external systems
Security Response Protocol
If security issue found:
- STOP immediately
- Fix CRITICAL issues before continuing
- Rotate any exposed secrets
- Review entire codebase for similar issues
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 · 55 lines · 311 tokens per session scan A 5fcb8aa4bf10
security is a cursor rule published in the GitHub repository timurgaleev/vibestack (6 stars, last pushed yesterday), licensed MIT. It adds 311 tokens to every session, about $0.0016 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-19.
Other cursor rules, from other repositories
tech-writer
Guide the AI to act as a Senior Technical Writer, focusing on clear and concise documentation.
ai-expert
Guide the AI to act as an AI/ML/MLOps Expert, integrating modern AI tooling, including AI agents, AI-powered IDEs, MCP servers, and online AI-powered tools.
back-end-dev
Guide the AI to act as a Senior Back-End Developer, focusing on modern back-end languages and frameworks.
product-owner
Guide the AI to act as a Senior Product Owner with strong UI/UX design capabilities, focusing on user-centric product development.
devops
Guide the AI to act as a Modern DevOps Engineer, specializing in AWS, Azure, and Google Cloud Platform.
architect
Guide the AI to act as a Software Architect, focusing on system design and scalability.