creating-rules

A set of rules for organising Cursor rule files, which guide the coding assistant in a project.

In plain words
What is it for?
Use it when creating Cursor rules: store them in /.cursor/rules/ and use descriptive kebab-case Markdown filenames.
Why use it?
It prevents rule files from being placed where Cursor may not expect them or from using unclear filenames.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/imazen/imageflow/creating-rules
Clone the repo
git clone --depth 1 https://github.com/imazen/imageflow

Made for: Cursor.

Per session 65 This file is loaded in full into every session.
When invoked 65 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00065 $0.00065
Opus 5 $0.00032 $0.00032
Sonnet 5 $0.00013 $0.00013
Haiku 4.5 $0.00006 $0.00006

Measured today against content hash 7566da2ec701, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

creating-rules 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 today.

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.

.cursor/rules/creating-rules.mdc · 7 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. today First seen · 7 lines · 65 tokens per session scan A 7566da2ec701

Subscribe to this mod's changes

creating-rules is a cursor rule published in the GitHub repository imazen/imageflow (4,412 stars, last pushed 2d ago), licensed AGPL-3.0. It adds 65 tokens to every session, about $0.0003 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-01.