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/project-overview-rule)<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/project-overview-rule"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/project-overview-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.00056 |
| Opus 5 | $0.00000 | $0.00028 |
| Sonnet 5 | $0.00000 | $0.00011 |
| Haiku 4.5 | $0.00000 | $0.00006 |
Grade A, and why
project-overview-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:
- project-overview-rule — 100% identical, 0 lines differ
- project-overview-rule — 100% identical, 0 lines differ
What it actually says
- This project is called PressThat.
- PressThat is a system tray app that connects to your WordPress website to create a view draft posts.
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 · 6 lines · 0 tokens per session scan A 337f40603c2e
project-overview-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 56 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
shopify-theme-dev-liquid
Best practices for Shopify theme development with Liquid, JavaScript, and CSS.
medusa-cursorrules
You are an expert senior software engineer specializing in modern web development, with deep expertise in TypeScript, Medusa, React.js, and TailwindCSS.
medusa
Medusa rules and best practices. These rules should be used when building applications with Medusa.
stripe
Stripe payment integration, webhooks, checkout, and subscriptions.
project-epic-template-cursorrules-prompt-file
Cursor rules for project development with epic template integration.
playwright-integration-testing-cursorrules-prompt-file
Cursor rules for Playwright development with integration testing.