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/claire-gong-18/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/claire-gong-18/awesome-cursorrules/general-guidelines)<a href="https://agentmods.dev/rules/claire-gong-18/awesome-cursorrules/general-guidelines"><img src="https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/general-guidelines.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.00101 | $0.00101 |
| Opus 5 | $0.00051 | $0.00051 |
| Sonnet 5 | $0.00020 | $0.00020 |
| Haiku 4.5 | $0.00010 | $0.00010 |
Grade A, and why
general-guidelines 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 4d 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.
This is a copy
100% identical to general-guidelines — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
- Assume the user has already set up the Next.js project with Tailwind CSS.
- Use environment variables for configuration following Next.js conventions.
- Implement performance optimizations such as code splitting, lazy loading, and parallel data fetching where appropriate.
- Ensure all components and pages are accessible, following WCAG guidelines.
- Utilize Next.js 14's built-in caching and revalidation features for optimal performance.
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.
- 4d ago First seen · 9 lines · 101 tokens per session scan A 41aa0f80526b
general-guidelines is a cursor rule published in the GitHub repository claire-gong-18/awesome-cursorrules (0 stars, last pushed 1y ago), licensed CC0-1.0. It adds 101 tokens to every session, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to general-guidelines, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
jawn
Cursor rule "jawn" from Helicone/helicone, covering helicone jawn controller and tanstack query integration, controller pattern, manager pattern, frontend hooks with tanstack query and type definitions.
sveltekit-typescript-guide-cursorrules-prompt-file
Cursor rules for SvelteKit development with TypeScript integration.
react-query-cursorrules-prompt-file
Cursor rules for React development with React Query integration.
next-js-server-actions
A guide for Next.js server actions, which let server-side code handle requests from an application interface, with validation and structured error responses.
data-fetching-rules-for-server-components
A set of rules for fetching data inside Next.js 14 server components, which render on the server rather than in the browser.
middleware
When you need create a middleware to protect some page of Next.js app.