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/ivangrynenko/cursorrulesWrote 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/ivangrynenko/cursorrules/vortex-scaffold-standards)<a href="https://agentmods.dev/rules/ivangrynenko/cursorrules/vortex-scaffold-standards"><img src="https://agentmods.dev/badge/rules/ivangrynenko/cursorrules/vortex-scaffold-standards/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/ivangrynenko/cursorrules/vortex-scaffold-standards"><img src="https://agentmods.dev/badge/rules/ivangrynenko/cursorrules/vortex-scaffold-standards.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.00000 | $0.00482 |
| Opus 5.5 | $0.00000 | $0.00193 |
| Sonnet 5.5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
vortex-scaffold-standards 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 1mo 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.
What it actually says
Vortex/DrevOps Scaffold Standards
Ensures proper usage of Vortex/DrevOps scaffold features and workflows.
actions:
-
type: enforce conditions:
-
pattern: "custom-download-db\.sh" message: "Use scripts/vortex/download-db.sh router script instead of custom implementation"
-
pattern: "drush\s+[a-z-]+\s+--uri=" message: "Use DRUPAL_SITE_URL environment variable instead of hardcoded URI"
-
pattern: "composer\s+require\s+[^-]" message: "Use Vortex's composer.json template and Renovate for dependency management"
-
pattern: "docker\s+exec\s+-it\s+\$\(docker-compose" message: "Use Ahoy commands for container interactions"
-
-
type: suggest message: | Vortex/DrevOps Best Practices:
- Use centralized workflow scripts from scripts/vortex/
- Leverage environment variables for configuration
- Use Renovate for automated dependency updates
- Follow the router script pattern for customizations
- Implement proper CI/CD integration
- Use provided tool configurations (PHPCS, PHPStan, etc.)
- Maintain documentation structure
- Ensure CI/CD pipelines include testing and deployment steps
- Document CI/CD processes in the README for clarity
-
type: validate conditions:
-
pattern: "^\s*source\s+\.env" message: "Use scripts/vortex/bootstrap.sh for environment setup"
-
pattern: "docker-compose\s+exec\s+cli\s+vendor/bin/" message: "Use provided Ahoy commands for tool execution"
-
metadata: priority: high version: 1.1
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.
- 1mo ago First seen · 57 lines · 482 tokens per session scan A 974a35879708
vortex-scaffold-standards is a cursor rule published in the GitHub repository ivangrynenko/cursorrules (88 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 482 tokens. 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-03.
Other cursor rules, from other repositories
django
Django: models, views, ORM best practices.
fastapi
FastAPI: Pydantic v2, dependency injection, async.
prisma
Prisma: schema modeling, queries, migrations.
supabase
Supabase: RLS, edge functions, realtime.
hono
Hono: routing, middleware, edge deployment patterns.
cloudflare-workers
Cloudflare Workers: edge computing, KV, D1, R2, Durable Objects.