o1-pro-template-system: Cursor rule for Cursor

.cursorrules

cursorrules is a cursor rule for Cursor from mckaywrigley/o1-pro-template-system. It costs 4,227 tokens per session, scanned A, original, MIT.

A project instruction file for a web application built with Next.js, Tailwind, and several backend and deployment tools. It describes the expected project structure and coding rules.

In plain words
What is it for?
Building or modifying pages, components, server actions, API routes, database code, authentication, payments, and deployment configuration.
Why use it?
It gives the agent consistent guidance about where code belongs and which technologies the app uses.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

This is mckaywrigley/o1-pro-template-system's own configuration. It tells Cursor how to work on o1-pro-template-system itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything o1-pro-template-system configures →

Reuse

Borrowing it

Nothing to install: this file belongs to mckaywrigley/o1-pro-template-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/mckaywrigley/o1-pro-template-system/main/.cursorrules
Clone the repo
git clone --depth 1 https://github.com/mckaywrigley/o1-pro-template-system

Made for: Cursor.

Wrote 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.

agentmods badge for cursorrules

README.md
[![agentmods](https://agentmods.dev/badge/rules/mckaywrigley/o1-pro-template-system/cursorrules/github.svg)](https://agentmods.dev/rules/mckaywrigley/o1-pro-template-system/cursorrules)
Your own site
<a href="https://agentmods.dev/rules/mckaywrigley/o1-pro-template-system/cursorrules"><img src="https://agentmods.dev/badge/rules/mckaywrigley/o1-pro-template-system/cursorrules/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.

agentmods 80×15 button for cursorrules

Your own site · 80×15
<a href="https://agentmods.dev/rules/mckaywrigley/o1-pro-template-system/cursorrules"><img src="https://agentmods.dev/badge/rules/mckaywrigley/o1-pro-template-system/cursorrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 4,227 This file is loaded in full into every session.
When invoked 4,227 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.04227 $0.04227
Opus 5.5 $0.01691 $0.01691
Sonnet 5.5 $0.00845 $0.00845
Haiku 4.5 $0.00423 $0.00423

Measured yesterday against content hash 13f8b27eac7a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cursorrules 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.

.cursorrules · 644 lines

How it starts

The opening of the file, as written. The whole thing — 644 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project Instructions

Use specification and guidelines as you build the app.

Write the complete code for every step. Do not get lazy.

Your goal is to completely finish whatever I ask for.

You will see tags in the code. These are context tags that you should use to help you understand the codebase.

Overview

This is a web app template.

Tech Stack

  • Frontend: Next.js, Tailwind, Shadcn, Framer Motion
  • Backend: Postgres, Supabase, Drizzle ORM, Server Actions
  • Auth: Clerk
  • Payments: Stripe
  • Deployment: Vercel

Project Structure

  • actions - Server actions
    • db - Database related actions
    • Other actions
  • app - Next.js app router
    • api - API routes
    • route - An example route
      • _components - One-off components for the route
      • layout.tsx - Layout for the route
      • page.tsx - Page for the route
  • components - Shared components
    • ui - UI components
    • utilities - Utility components
  • db - Database
    • schema - Database schemas
  • lib - Library code
    • hooks - Custom hooks
  • prompts - Prompt files
  • public - Static assets
  • types - Type definitions

Rules

Follow these rules when building the app.

General Rules

  • Use @ to import anything from the app unless otherwise specified
  • Use kebab case for all files and folders unless otherwise specified
  • Don't update shadcn components unless otherwise specified
Env Rules
  • If you update environment variables, update the .env.example file
  • All environment variables should go in .env.local
  • Do not expose environment variables to the frontend
  • Use NEXT_PUBLIC_ prefix for environment variables that need to be accessed from the frontend
  • You may import environment variables in server actions and components by using process.env.VARIABLE_NAME
Type Rules

Follow these rules when working with types.

  • When importing types, use @/types
  • Name files like example-types.ts
  • All types should go in types
  • Make sure to export the types in types/index.ts
  • Prefer interfaces over type aliases
  • If referring to db types, use @/db/schema such as SelectTodo from todos-schema.ts

Read the full file on GitHub · 644 lines

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 · 644 lines · 4,227 tokens per session scan A 13f8b27eac7a

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository mckaywrigley/o1-pro-template-system (142 stars, last pushed 1y ago), licensed MIT. It adds 4,227 tokens to every session, about $0.0169 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-10-14.