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.
npx agentmods add rules/thesethrose/devrules/create-cursor-rulegit clone --depth 1 https://github.com/TheSethRose/DevRulesWhat 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 | $0.00019 | $0.00657 |
| Opus 5 | $0.00010 | $0.00329 |
| Sonnet 5 | $0.00004 | $0.00131 |
| Haiku 4.5 | $0.00002 | $0.00066 |
Grade A, and why
Create-Cursor-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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task: Create Cursor Rule
You are assisting the user in creating a new Cursor rule (.mdc) file.
Your goal is to generate a well-structured rule file adhering to the established project standards.
Process
-
Gather Requirements: Ask the user for the following information:
- Rule Purpose/Goal: What should this rule help the AI achieve or understand? (This will inform the
descriptionand main content). - Target Directory: Where should the new rule file be placed? (
tasks/,languages/,technologies/, or rootrules/?) - Proposed Filename: What should the
.mdcfile be named? (e.g.,GoLang.mdc,Generate-Commit-Message.mdc). - Activation Globs: Which file patterns should automatically trigger this rule? (Provide examples like
"**/*.go"or"*commit*"). If none, use"". - Always Apply?: Should this rule always be applied regardless of file context? (
trueorfalse, typicallyfalseunless it's a core rule modification). - Core Content Ideas: What key instructions, guidelines, or examples should be included in the rule body?
- Rule Purpose/Goal: What should this rule help the AI achieve or understand? (This will inform the
-
Structure the Rule: Create the content for the new
.mdcfile using the standard format:- Header Block: Generate the YAML frontmatter with
description,globs(comma-separated string), andalwaysApplybased on user input. - Main Title: Use the rule's purpose or filename as the main
#title. - Introduction: Briefly state the rule's objective.
- Key Sections: Organize the core content using Markdown headings (
##,###), lists, and code blocks as appropriate (e.g.,## Guidelines,## Best Practices,## Examples).
- Header Block: Generate the YAML frontmatter with
-
Generate the File Content: Provide the complete content for the new rule file within a single code block, ready for the user to save.
Formatting Requirements
- Header: Must start with
---, containdescription(quoted string),globs(quoted, comma-separated string),alwaysApply(booleantrue/false), and end with---. - Content: Use clear Markdown for structure and readability.
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.
- yesterday First seen · 61 lines · 19 tokens per session scan A 9e81ee7ec7ca
Create-Cursor-Rule is a cursor rule published in the GitHub repository TheSethRose/DevRules (25 stars, last pushed 1y ago), licensed MIT. It adds 19 tokens to every session and 657 once invoked, about $0.0001 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-08-30.
Other cursor rules, from other repositories
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
prpm-json-best-practices
Best practices for structuring prpm.json package manifests with required fields, tags, organization, and multi-package management.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
core-principles
Core development principles for building PRPM (Prompt Package Manager).
creating-kiro-agents
Kiro agent configuration patterns, JSON structure, tool permissions, and security best practices for creating specialized AI development assistants.