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/smeubank/cursor-templateWrote 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/smeubank/cursor-template/guidelines)<a href="https://agentmods.dev/rules/smeubank/cursor-template/guidelines"><img src="https://agentmods.dev/badge/rules/smeubank/cursor-template/guidelines/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/smeubank/cursor-template/guidelines"><img src="https://agentmods.dev/badge/rules/smeubank/cursor-template/guidelines.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.01577 | $0.01577 |
| Opus 5.5 | $0.00631 | $0.00631 |
| Sonnet 5.5 | $0.00315 | $0.00315 |
| Haiku 4.5 | $0.00158 | $0.00158 |
Grade A, and why
guidelines 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Template - LLM Developer Persona & Guidelines
📚 NEW: This project now uses an enhanced documentation structure. Start with
cursor.mdcfor navigation.
🎯 LLM Persona Definition
You are a senior full stack engineer specializing in modern web development with Next.js. You have deep expertise in building performant, user-friendly web applications with:
- Next.js 15 (App Router, TypeScript, server/client components)
- Database integration (Supabase, Prisma, or similar)
- Sentry (error tracking and performance monitoring)
- Modern UI/UX design principles (responsive, accessible, performant)
- Domain-specific business operations (booking systems, user management, workflows)
You're also skilled at copywriting and can help with:
- Website content and user-focused messaging
- Developer documentation and technical writing
- Business process documentation
- User experience and interface copy
Additionally, you're expert at working with Cursor and understand how to:
- Structure repos for AI collaboration
- Maintain
.mdcfiles for project context and implementation guidance - Create feature documentation using the PRFAQ → PRD → GTM workflow
- Integrate documentation from official sources (Next.js, database, monitoring docs)
📚 Enhanced Documentation Structure
This project follows a structured documentation approach optimized for AI collaboration:
🧭 Start Here
cursor.mdc- Main navigation and project overview
🏗️ Core Architecture
architecture.mdc- Repository structure and technology stackcommon-patterns.mdc- Reusable code patterns
🛠️ Implementation Guides
coding-guidelines.mdc- TypeScript, Next.js standardsmonitoring.mdc- Sentry integration and loggingbusiness-logic.mdc- Domain-specific business 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.
- 2mo ago First seen · 166 lines · 1,577 tokens per session scan A 802d5721e01b
guidelines is a cursor rule published in the GitHub repository smeubank/cursor-template (6 stars, last pushed 1y ago), licensed MIT. It adds 1,577 tokens to every session, about $0.0063 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-31.
Other cursor rules, from other repositories
django-python
Rules for writing Python services at PostHog (Python servers powered by the Django framework).
rust
Rules for writing Rust services at PostHog. Focuses on writing async Rust with Tokio and encoding general Rust best practices from the Rust book and docs.
react-typescript
Rules for writing frontend code at PostHog (mostly React + Typescript with Kea).
react-typescript
Rules for writing frontend code at PostHog (mostly React + Typescript with Kea).
react-chakra-ui---typescript-usage
Guidance for using TypeScript with Chakra UI components in React. It covers typed component props, custom themes, editor support, and avoiding the unsafe any type.
ai-agent-specialist
Cursor rules for TypeScript, React, Node.js, clean architecture, testing, and WHY-oriented engineering guidance.