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/abderrahimghazali/cursor-rules/govcms-saasgit clone --depth 1 https://github.com/abderrahimghazali/cursor-rulesWhat 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.00037 | $0.00843 |
| Opus 5 | $0.00018 | $0.00421 |
| Sonnet 5 | $0.00007 | $0.00169 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade A, and why
govcms-saas 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 2d 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
name: govcms-distribution-development-standards id: govcms_distribution
description: > This rule defines the constraints and best practices for working with GovCMS Distribution projects. The primary focus is theme-level development only, as the distribution's infrastructure and core functionality should remain unchanged.
project_identification:
- "docker-compose.yml with GovCMS-specific services"
- ".lagoon.yml configuration"
- ".ahoy.yml for GovCMS commands"
- "Standard GovCMS directory structure"
- "The .version file will contain 'type: saas'"
development_constraints: restricted_areas: - "docker-compose.yml" - ".docker/" - ".lagoon.yml" - ".lagoon.env" - ".ahoy.yml" - "Core infrastructure files" - "Docker-related configurations" - "CI/CD configurations (.gitlab-ci.yml)" - "Root-level configuration files" allowed_areas: - name: "Theme Development" location: "themes/" modifications: - "Twig templates" - "CSS/SCSS files" - "JavaScript files" - "Theme hooks in .theme files" - "Theme-specific libraries" - "Theme configuration" - "Theme-level preprocess functions" - "Theme-level template suggestions" - name: "Theme-Level Functionality" note: "Implement all custom functionality within theme using relevant theme hooks and practices" modifications: - "hook_preprocess_ functions" - "theme-specific JavaScript" - "Twig templates and includes" - "Theme hooks" - "Library definitions" - "CSS/SCSS modifications"
best_practices: theme_development: - "Follow Drupal 10 theming standards" - "Use Twig templates for markup modifications" - "Implement responsive design patterns" - "Use theme hooks for dynamic content" - "Maintain accessibility standards" - "Use BEM methodology for CSS" - "Implement JavaScript as behaviors" performance: - "Optimize theme assets" - "Use Drupal's library system" - "Implement lazy loading where appropriate" - "Minimize CSS/JavaScript file sizes" security: - "Sanitize all output in Twig templates" - "Use Drupal's Form API for any forms" - "Implement proper XSS protection" - "Follow Drupal security best practices"
implementation_guidelines:
- "All customizations must be contained within the theme directory"
- "Use theme hooks instead of custom modules"
- "Leverage Drupal's theme layer APIs"
- "Maintain backwards compatibility"
- "Document all theme modifications"
- "Use responsive images and optimize assets"
- "Follow Drupal coding standards"
error_prevention:
- "Prevent modifications to infrastructure files"
- "Ensure all development stays within theme boundaries"
- "Avoid custom module development"
- "No modifications to distribution core files"
file_patterns: protected: - "docker-compose.yml" - ".docker/" - ".lagoon.yml" - ".lagoon.env" - ".ahoy.yml" - ".gitlab-ci.yml" - "behat.yml" - "phpcs.xml" - "composer." allowed: - "themes//css//" - "themes//js//" - "themes//templates//" - "themes//.theme" - "themes//theme-settings.php" - "themes/*/config//" - "themes//images//" - "themes//fonts//" - "themes//.libraries.yml" - "themes//*.info.yml"
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.
- 2d ago First seen · 110 lines · 37 tokens per session scan A 809cf6f9cd04
govcms-saas is a cursor rule published in the GitHub repository abderrahimghazali/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 37 tokens to every session and 843 once invoked, about $0.0002 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-31.
Other cursor rules, from other repositories
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
cursorrules
You are a disciplined senior engineer working with someone who may be a domain expert, not a programmer. Build it correctly and safely, not just fast.
cursorrules
Cursor rule "cursorrules" from BlueBirdBack/godot-cursorrules, covering godot 4.4 game development .cursorrules, core development guidelines, code style, naming conventions and scene organization.
new_feature
You are an expert Product Owner and Technical Lead focused on helping users define and plan new features through collaborative discovery and structured documentation.
new_project
You are an expert Product Owner focused on helping users define new software projects through collaborative vision creation.