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/key-conventions)<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/key-conventions"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/key-conventions.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.00087 |
| Opus 5 | $0.00000 | $0.00044 |
| Sonnet 5 | $0.00000 | $0.00017 |
| Haiku 4.5 | $0.00000 | $0.00009 |
Grade A, and why
key-conventions 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
1 near-identical copy found in the catalogue:
- key-conventions — 100% identical, 0 lines differ
What it actually says
Key Conventions
- Follow Astro's Style Guide for consistent code formatting.
- Use TypeScript for enhanced type safety and developer experience.
- Implement proper error handling and logging.
- Leverage Astro's RSS feed generation for content-heavy sites.
- Use Astro's Image component for optimized image delivery.
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 · 11 lines · 0 tokens per session scan A edbc4ea064fa
key-conventions 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 87 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
nextjs-tanstack-query-cursorrules-prompt-file
Cursor rules for Next.js App Router with TanStack Query v5, covering the HydrationBoundary pattern, Server Actions as mutations, and optimistic updates.
nextjs-tanstack-query
Next.js App Router combined with TanStack Query v5 — HydrationBoundary pattern, Server Actions as mutations, optimistic updates, and infinite scroll.
nextjs-supabase-shadcn-pwa-cursorrules-prompt-file
Cursor rules for Nextjs Supabase Shadcn Pwa.
sveltekit-tailwindcss-typescript-cursorrules-promp
Cursor rules for SvelteKit development with Tailwind CSS and TypeScript integration.
astro-typescript-cursorrules-prompt-file
Cursor rules for Astro development with TypeScript integration.
nextjs-typescript-tailwind-cursorrules-prompt-file
Cursor rules for Next.js development with TypeScript and Tailwind CSS integration.