derived-cursor-rules

A set of coding rules created from a project's earlier AI conversations. It records project conventions for areas such as the technology stack, documentation, releases, debugging, builds, and VS Code setup.

In plain words
What is it for?
Use it as background guidance when working on the project, particularly when building related packages, configuring TypeScript dependencies, or setting up VS Code debugging.
Why use it?
It gives future coding sessions consistent project-specific guidance instead of making the agent rediscover past decisions. It can help avoid build-order and TypeScript configuration mistakes.

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/aculich/codegen-preflight/derived-cursor-rules
Clone the repo
git clone --depth 1 https://github.com/aculich/codegen-preflight

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 450 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original 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.00000 $0.00450
Opus 5 $0.00000 $0.00225
Sonnet 5 $0.00000 $0.00090
Haiku 4.5 $0.00000 $0.00045

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

Security

Grade A, and why

derived-cursor-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 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.

.cursor/rules/derived-cursor-rules.mdc · 32 lines

What it actually says

HEADERS

TECH STACK

PROJECT DOCUMENTATION & CONTEXT SYSTEM

WORKFLOW & RELEASE RULES

DEBUGGING

When debugging Typescript projects with interdependencies:

  1. Ensure the correct build order is enforced. Build dependencies (e.g. @codegen-preflight/mcp-server) before dependents (e.g. extension). Update the root package.json to reflect the correct build order. The build script should enforce this order (e.g., "build": "npm run build --workspace=@codegen-preflight/mcp-server && npm run build --workspace=codegen-preflight").
  2. To resolve Typescript module resolution issues, add type declarations (packages/extension/src/mcp-server-types.d.ts) for dynamic imports.
  3. Enable Typescript project references: Update tsconfig.json files to support project references and set "composite": true in the dependency's tsconfig.json. Also ensure allowSyntheticDefaultImports is set to true and noResolve is set to false in the dependent's (packages/extension) tsconfig.json.
  4. Create .vscode/launch.json and tasks.json for F5 debugging in VS Code.
  5. Configure the launch configuration to use the correct paths for the extension workspace.

GIT

  1. When making changes that affect the build process or inter-project dependencies (e.g. Typescript project references), ensure the following files are committed:
    • package.json (especially the build script)
    • packages/extension/tsconfig.json
    • packages/mcp-server/tsconfig.json
    • Any necessary type declaration files (e.g., packages/extension/src/mcp-server-types.d.ts)
    • .vscode/launch.json & tasks.json (optional, but recommended for improved developer experience)
  2. Add the following to .gitignore:
    • *.tsbuildinfo
    • .specstory/
    • .cursor/rules/derived-cursor-rules.mdc
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. yesterday First seen · 32 lines · 450 tokens per session scan A fc6b589461bb

Subscribe to this mod's changes

derived-cursor-rules is a cursor rule published in the GitHub repository aculich/codegen-preflight (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 450 tokens. 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-31.