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/project-definition-templategit 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.00000 | $0.00718 |
| Opus 5 | $0.00000 | $0.00359 |
| Sonnet 5 | $0.00000 | $0.00144 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
project-definition-template 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
Comprehensive Project Definition Template
This rule enforces best practices for documenting project context, ensuring clarity and maintainability through well-documented README files and documentation.
actions:
-
type: enforce conditions:
-
pattern: "## Project Purpose" message: "Define the purpose of the project in the README file, including its goals and objectives."
-
pattern: "## Technical Stack" message: "List the technical stack used in the project in the README file, including language versions and frameworks."
-
pattern: "## Folder Structure" message: "Document the folder structure in the README file with a brief explanation for each significant directory."
-
pattern: "## Customizations" message: "Include any custom themes, modules, or libraries in the README file, explaining their functionality."
-
pattern: "## Libraries" message: "List any third-party libraries used in the project in the README file, including versions for reproducibility."
-
pattern: "## Setup Instructions" message: "Provide clear setup instructions in the README to help new contributors or users get started."
-
pattern: "## Contribution Guidelines" message: "Document contribution guidelines if the project is open-source or team-based."
-
-
type: suggest message: | Project Definition Best Practices:
- README and Docs: Use both README.md for an overview and /docs/ for detailed documentation.
- Project Purpose: Clearly articulate why the project exists, its objectives, and who it serves.
- Technical Stack: Include all technologies, versions, and possibly why each was chosen.
- Folder Structure: Use tree diagrams or simple bullet points to describe the project's layout.
- Customizations: Explain any custom code, including its purpose and how it integrates with the project.
- Libraries: Detail external dependencies, why they're used, and how to manage them (e.g., npm, composer).
- Setup Instructions: Provide step-by-step guidance for setting up the project environment.
- Contribution Guidelines: Outline how to contribute, including coding standards, branch management, and pull request process.
- License: Include information about the project's licensing for legal clarity.
- Roadmap: Optionally, add a roadmap section to discuss future plans or features.
-
type: validate conditions:
-
pattern: "## Project Purpose" message: "Ensure the project purpose is clearly defined for understanding the project's intent."
-
pattern: "## Technical Stack" message: "Ensure the technical stack is documented to aid in tech stack comprehension."
-
pattern: "## Folder Structure" message: "Ensure the folder structure is outlined for navigation ease."
-
pattern: "## Customizations" message: "Ensure customizations are documented for understanding unique project elements."
-
pattern: "## Libraries" message: "Ensure libraries are listed for dependency management."
-
pattern: "## Setup Instructions" message: "Ensure setup instructions are included to facilitate onboarding."
-
metadata: priority: medium 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.
- 2d ago First seen · 79 lines · 0 tokens per session scan A cd16de16dc29
project-definition-template is a cursor rule published in the GitHub repository abderrahimghazali/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 718 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-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.