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/praveen-palanisamy/autodemo/cursorrulesgit clone --depth 1 https://github.com/praveen-palanisamy/autodemoWrote 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/praveen-palanisamy/autodemo/cursorrules)<a href="https://agentmods.dev/rules/praveen-palanisamy/autodemo/cursorrules"><img src="https://agentmods.dev/badge/rules/praveen-palanisamy/autodemo/cursorrules.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.1 | $0.00182 | $0.00182 |
| Opus 5 | $0.00091 | $0.00091 |
| Sonnet 5 | $0.00036 | $0.00036 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
cursorrules 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
Always remember to save working checkpoints and commit code after implementing a feature or fixing and ensuring that the app is in a working state. Carefully review and stage all relevant changes, commit with a descriptive message. Do not leave completed feature or fix work uncommitted — stage and commit before ending the session unless the user explicitly asked not to. See AGENTS.md for agent workflow details. Ensure you always prioritize fixes in the code or create scripts and run them and don't run one off comands in the commandline . It needs to be reproducible. Ensure you maintain idempotency with scripts. Keep docs, developer docs, README updated and reflecting the current/latest status and remove any stale information or detail especially after code changes. Prefer modular, reusable SOLID code and avoid large number of lines in a single file. Use mermaid or kroki diagrams instead of ascii art for block, flow and other systems design.
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 · 5 lines · 182 tokens per session scan A b57771c3866c
cursorrules is a cursor rule published in the GitHub repository praveen-palanisamy/autodemo (3 stars, last pushed 2mo ago), licensed MIT. It adds 182 tokens to every session, about $0.0009 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
cursor-fable-rules
Fable coding lifecycle discipline and situational awareness for Cursor.
release-checklist
What to update with each code change or version release.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
cli-error-handling
CLI command error handling patterns.