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/steipete/agent-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/steipete/agent-rules/cursor-rules-meta-guide)<a href="https://agentmods.dev/rules/steipete/agent-rules/cursor-rules-meta-guide"><img src="https://agentmods.dev/badge/rules/steipete/agent-rules/cursor-rules-meta-guide/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/steipete/agent-rules/cursor-rules-meta-guide"><img src="https://agentmods.dev/badge/rules/steipete/agent-rules/cursor-rules-meta-guide.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.00375 | $0.00375 |
| Opus 5.5 | $0.00150 | $0.00150 |
| Sonnet 5.5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
cursor-rules-meta-guide 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 1mo 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
8 near-identical copies found in the catalogue:
- cursor_rules — 100% identical, 0 lines differ
- cursor_rules — 100% identical, 5 lines differ
- cursor_rules — 100% identical, 5 lines differ
- cursor_rules — 100% identical, 0 lines differ
- cursor_rules — 100% identical, 0 lines differ
- cursor_rules — 100% identical, 0 lines differ
- cursor_rules — 100% identical, 0 lines differ
- cursor_rules — 100% identical, 0 lines differ
What it actually says
-
Required Rule Structure:
--- description: Clear, one-line description of what the rule enforces globs: path/to/files/*.ext, other/path/**/* alwaysApply: boolean --- - **Main Points in Bold** - Sub-points with details - Examples and explanations -
File References:
- Use
[filename](mdc:path/to/file)(filename) to reference files - Example: prisma.mdc for rule references
- Example: schema.prisma for code references
- Use
-
Code Examples:
- Use language-specific code blocks
// ✅ DO: Show good examples const goodExample = true; // ❌ DON'T: Show anti-patterns const badExample = false; -
Rule Content Guidelines:
- Start with high-level overview
- Include specific, actionable requirements
- Show examples of correct implementation
- Reference existing code when possible
- Keep rules DRY by referencing other rules
-
Rule Maintenance:
- Update rules when new patterns emerge
- Add examples from actual codebase
- Remove outdated patterns
- Cross-reference related rules
-
Best Practices:
- Use bullet points for clarity
- Keep descriptions concise
- Include both DO and DON'T examples
- Reference actual code over theoretical examples
- Use consistent formatting across rules
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.
- 1mo ago First seen · 53 lines · 375 tokens per session scan A 60e89f6f5894
cursor-rules-meta-guide is a cursor rule published in the GitHub repository steipete/agent-rules (5,677 stars, last pushed 5mo ago), licensed MIT. It adds 375 tokens to every session, about $0.0015 per session on Opus 5.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-08-30.
Other cursor rules, from other repositories
paperfit
PaperFit project rule for LaTeX visual typesetting optimization.
previews
Cloudflare Worker Previews pipeline - credential-free Preview build then cf previews deploy, cf previews delete, Wrangler-only secrets, Access before arming, agent loop.
react
React 19 SPA - client-only, layout and #/ imports, no fetch in useEffect, Compiler memo policy, providers, splitting, React Doctor.
read-xlsx
Reading, writing, diffing, and repairing spreadsheets (.xlsx) for AI agents via the xfa MCP server.
service-bindings
Worker-to-Worker RPC - bindings.worker() by name, WorkerEntrypoint callee, typed RPC deferred, requestId propagation.
workers-cache
Workers Cache - Cache-Control, gateway exports cache off, RPC vs fetch.