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.
git clone --depth 1 https://github.com/paulpham157/paul-s-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/paulpham157/paul-s-cursor-rules/automation-script-rule)<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/automation-script-rule"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/automation-script-rule.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.00000 | $0.00068 |
| Opus 5 | $0.00000 | $0.00034 |
| Sonnet 5 | $0.00000 | $0.00014 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
automation-script-rule 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 3d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- automation-script-rule — 100% identical, 0 lines differ
- automation-script-rule — 100% identical, 0 lines differ
What it actually says
When creating or modifying automation scripts:
- Ensure scripts are modular and reusable.
- Implement robust error handling and logging.
- Document the purpose and usage of each script clearly.
- Prioritize efficiency and performance in script 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.
- 3d ago First seen · 9 lines · 0 tokens per session scan A e3364a3f1ca0
automation-script-rule is a cursor rule published in the GitHub repository paulpham157/paul-s-cursor-rules (27 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 68 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-09-03.
Other cursor rules, from other repositories
vscode
VS Code: settings, extensions, workspace config.
file-organization
Maintain perfect project organization. Never create files in wrong locations.
notion
Cursor rule "notion" from gabornyergesX/cursorrules, covering notion integration rules, mcp integration, working with notion mcp server, mcp-enhanced workflows and documentation structure.
reply-tracker
Reply Tracker (also known as Reply Zero) lets the user which emails need a reply for them and those they're awaiting a reply on. It updates the labels for the thread automatically in Gmail.
pyspark-etl-best-practices-cursorrules-prompt-file
Cursor rules for PySpark ETL development with code style, joins, window functions, map operations, and Iceberg patterns.
project-epic-template-cursorrules-prompt-file
Cursor rules for project development with epic template integration.