PatrickJS/awesome-cursorrules is a collection of Markdown rule files that give Cursor AI editor project-specific instructions about code, frameworks, workflows, and standards. Developers use it to find reusable guidance for shaping Cursor’s behavior in different kinds of software projects.
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/PatrickJS/awesome-cursorrulesWrote 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/patrickjs/awesome-cursorrules/landing-page-image-quality-cursorrules-prompt-file)<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/landing-page-image-quality-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/landing-page-image-quality-cursorrules-prompt-file/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/landing-page-image-quality-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/landing-page-image-quality-cursorrules-prompt-file.svg" alt="Reviewed on agentmods" width="80" 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.00352 | $0.00352 |
| Opus 5 | $0.00176 | $0.00176 |
| Sonnet 5 | $0.00070 | $0.00070 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
landing-page-image-quality-cursorrules-prompt-file 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
Landing Page Image Quality
When generating or editing user-facing pages, use real, relevant visual assets instead of placeholder image services.
Image Sources
- Do not commit
placehold.co,via.placeholder.com,dummyimage.com,picsum.photos, random image URLs, or broken/deprecated image services. - Prefer committed project assets, product screenshots, generated assets approved by the user, or stable URLs from an approved image provider.
- Before using a third-party image, confirm the license and attribution requirements are compatible with the project.
- Avoid hotlinking images from arbitrary websites.
Asset Quality
- Match images to the actual content, product, place, object, or user state they represent.
- Do not use vague atmospheric images when the user needs to inspect a product, feature, workflow, or interface.
- Use consistent aspect ratios for repeated cards or gallery items.
- Provide explicit
widthandheightattributes or CSS aspect-ratio constraints to prevent layout shift. - Use optimized formats and sizes appropriate for the target framework.
Accessibility
- Every informative image must have specific
alttext that describes the image's purpose in context. - Decorative images must use empty alt text and should not be announced to assistive technology.
- Do not put essential text only inside an image.
Implementation Checks
- Ensure image paths resolve in the built application.
- Check responsive behavior at mobile and desktop widths.
- Verify that loading, error, and empty states do not leave broken image icons in production UI.
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 · 36 lines · 352 tokens per session scan A 4b2648b92e9f
landing-page-image-quality-cursorrules-prompt-file is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,737 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 352 tokens to every session, about $0.0018 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-09-03.
Other cursor rules, from other repositories
shadcn-ui
Cursor rule "shadcn-ui" from nedcodes-ok/cursorrules-collection, covering shadcn/ui rules, component usage, styling, forms and dialog/sheet/modal patterns.
storybook
Storybook: CSF3 stories, args, decorators, docs.
accessibility
Web accessibility best practices for WCAG compliance and inclusive design.
shadcn-ui
Cursor rule "shadcn-ui" from Renvia-code/best-cursor-rules, covering shadcn/ui best practices, installation, initial setup, initialize shadcn/ui in your project and add components as needed.
novo-elements-integration-rules
description: Rules specific to integrating Novo Elements library, including referencing documentation and GitHub repository. globs: /.ts.
ui-and-styling-rules
description: Rules for creating user interfaces and applying consistent styling across the extension's UI elements. globs: /popup.html, /options.html, /.css.