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-saas-project-documentation-creationgit clone --depth 1 https://github.com/abderrahimghazali/cursor-rulesWrote 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/abderrahimghazali/cursor-rules/govcms-saas-project-documentation-creation)<a href="https://agentmods.dev/rules/abderrahimghazali/cursor-rules/govcms-saas-project-documentation-creation"><img src="https://agentmods.dev/badge/rules/abderrahimghazali/cursor-rules/govcms-saas-project-documentation-creation.svg" alt="Measured on agentmods" 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 | $0.00037 | $0.00519 |
| Opus 5 | $0.00018 | $0.00260 |
| Sonnet 5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
govcms-saas-project-documentation-creation 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 5d 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_documentation_generator description: Generate comprehensive documentation for GovCMS SaaS projects version: 1.0.0 filters:
-
type: file_extension pattern: "(php|yml|js|css|twig|md)$"
-
type: file_path pattern: "(themes/custom|modules/custom|templates|docs)" actions:
-
type: suggest message: |
GovCMS SaaS Documentation Generator
Framework Detection
- Scan codebase for CSS frameworks (Tailwind, Bootstrap, Foundation, etc.)
- Identify JS libraries (Alpine.js, Vue, React, etc.)
- Confirm Drupal 10+ compatibility
- Check for GovCMS SaaS constraints compliance
Documentation Structure
Generate these core documentation files:
1. Project Documentation (project-documentation.md)
- Project Overview
- Platform Architecture (GovCMS SaaS)
- Components & Features
- Development Workflow
- Deployment Process
- Maintenance Guidelines
- SaaS Constraints & Workarounds
2. Theme Documentation (theme-documentation.md)
- Technical Specifications
- Theme Structure & Regions
- CSS Framework Implementation
- JavaScript Functionality
- Responsive Design Approach
- Accessibility Compliance
- Customization Guidelines
3. Content Management (content-management-guidelines.md)
- Content Types & Fields
- Media Management
- Editorial Guidelines
- Content Workflow
- SEO Best Practices
- Accessibility Requirements
4. Testing Guidelines (testing-guidelines.md)
- Theme Compilation Testing
- Responsive Testing
- Functional Testing
- Accessibility Testing
- Performance Testing
- Browser Compatibility
Output Format
- Use Markdown with proper heading hierarchy
- Include code examples
- Add relevant screenshots
- Link between documentation sections
- Include version information and dates
GovCMS SaaS Constraints
- Emphasize theme-only customizations (no custom modules)
- Focus on configuration-based solutions
- Document admin UI customizations
- Include Lagoon/platform-specific details
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.
- 5d ago First seen · 73 lines · 37 tokens per session scan A 06bafa4b447d
govcms-saas-project-documentation-creation 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 519 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.
typescript-type-safety
Use when encountering TypeScript any types, type errors, or lax type checking - eliminates type holes and enforces strict type safety through proper interfaces, type guards, and module augmentation.
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.