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-cicd-standards)<a href="https://agentmods.dev/rules/ivangrynenko/cursorrules/vortex-cicd-standards"><img src="https://agentmods.dev/badge/rules/ivangrynenko/cursorrules/vortex-cicd-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-cicd-standards"><img src="https://agentmods.dev/badge/rules/ivangrynenko/cursorrules/vortex-cicd-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.00429 |
| Opus 5.5 | $0.00000 | $0.00172 |
| Sonnet 5.5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
vortex-cicd-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 CI/CD Standards
Ensures proper CI/CD and dependency management configuration.
actions:
-
type: enforce conditions:
-
pattern: "workflows:\s+version:\s*2\.1" message: "Use Vortex's CircleCI configuration template"
-
pattern: ""extends":\s*\[\s*"config:base"\s*\]" message: "Extend Vortex's Renovate configuration for Drupal projects"
-
pattern: "steps:\s+- run:\s+name:\s+Install dependencies" message: "Use scripts/vortex/provision.sh for consistent provisioning"
-
-
type: suggest message: | CI/CD Best Practices:
- Use dual schedules for Drupal updates
- Configure automated PR assignments
- Enable deployment notifications
- Use provided test scaffolds
- Implement proper caching strategy
- Configure branch protection rules
- Use standardized job naming
-
type: validate conditions:
-
pattern: ""packageRules":\s*\[\s*\{\s*"matchPackagePatterns":\s*\["^drupal/core" message: "Configure separate update schedules for Drupal core and contrib"
-
pattern: "jobs:\s+build_test:" message: "Include all required test jobs from Vortex template"
-
pattern: "- store_test_results:" message: "Enable test results storage for better CI visibility"
-
metadata: priority: critical version: 1.0
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 · 53 lines · 0 tokens per session scan A 7af3dc1330fc
vortex-cicd-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 429 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
git-workflow
Git workflow: commits, branches, PRs, history management.
turborepo
Turborepo: monorepo structure, caching, task pipelines.
ci-cd
CI/CD: pipelines, deployment, automation.
github-actions-standards
Ensures GitHub Actions workflows follow best practices and use the latest action versions.
git-commit-conventions
Cursor rule "git-commit-conventions" from brettdavies/cursor-template, covering commit message conventions, mandatory process sequence, 1. capture changes [required], 2. process diff file [required] and 3. generate commit message [required].
git-workflow
Step-by-step instructions for Git workflow, including branch management, commits, and PR process.