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/rosendolu/cursor-rules-deploy/devgit clone --depth 1 https://github.com/rosendolu/cursor-rules-deployWhat 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.00490 |
| Opus 5 | $0.00000 | $0.00245 |
| Sonnet 5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
dev 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.
This is a copy
100% identical to dev — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agile Workflow and core memory procedure RULES that MUST be followed EXACTLY!
- When coming online, you will first check if a .ai/*.story.md file exists with the highest sequence number and review the story so you know the current phase of the project.
- Always use the
.cursor/templates/template-story.mdfile as a template for the story. The story will be named -.story.md added to the .ai folder- Example: .ai/story-1.story.md, .ai/story-2.story.md
- You will ALWAYS wait for the user to mark the story status as approved before doing ANY work outside of the story file.
- You will run tests and ensure tests pass before going to the next subtask within a story.
- You will update the story file as subtasks are completed.
- Once a Story is complete, you will generate a draft of the next story and wait on approval before proceeding.
- If there is no story when you come online that is not in draft or in progress status, request the user work with the PM to draft the next story.
During Development
- Update story files as subtasks are completed.
- If you are unsure of the next step, ask the user for clarification, and then update the story as needed to maintain a very clear memory of decisions.
- Reference the .ai/architecture.md if the story is inefficient or needs additional technical documentation so you are in sync with the Architects plans.
- When prompted by the user with 'update story', update the current story to:
- Reflect the current state.
- Clarify next steps.
- Ensure the chat log in the story is up to date with any chat thread interactions
- Continue to verify the story is correct and the next steps are clear.
- Remember that a story is not complete if you have not also run ALL stories and verified all stories pass.
- Do not tell the user the story is complete, or mark the story as complete unless you have run ALL the tests.
YOU DO NOT NEED TO ASK to:
- Run unit Tests during the development process until they pass.
- Update the story AC and tasks as they are completed.
- Update the story file with the chat log or other updates to retain the best possible memory of the story status.
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 · 35 lines · 0 tokens per session scan A 54dbb1b319d2
dev is a cursor rule published in the GitHub repository rosendolu/cursor-rules-deploy (37 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 490 tokens. A static security scan graded it A with 0 findings. It is 100% identical to dev, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.