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/project-context)<a href="https://agentmods.dev/rules/smeubank/cursor-template/project-context"><img src="https://agentmods.dev/badge/rules/smeubank/cursor-template/project-context/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/project-context"><img src="https://agentmods.dev/badge/rules/smeubank/cursor-template/project-context.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.01983 | $0.01983 |
| Opus 5.5 | $0.00793 | $0.00793 |
| Sonnet 5.5 | $0.00397 | $0.00397 |
| Haiku 4.5 | $0.00198 | $0.00198 |
Grade A, and why
project-context 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Context Template
🎯 Project Overview
[Your Project Name] is a modern web application built with Next.js, featuring [brief description of your project's purpose].
🏗️ Repository Structure
/app- CURRENT DEVELOPMENT - Next.js App Router application (port 3000)/admin- Admin dashboard (port 3001) [if applicable]/api- API routes and server-side logic/components- Reusable UI components/lib- Utility functions and configuration
🔧 Technology Stack
- Frontend: Next.js 14+ (App Router), TypeScript, Tailwind CSS
- Backend: [Your backend choice - Supabase, Prisma, etc.]
- UI Library: [Your UI library - ShadCN/UI, Chakra UI, etc.]
- Monitoring: [Your monitoring solution - Sentry, LogRocket, etc.]
- Deployment: [Your deployment platform - Vercel, Netlify, etc.]
📂 Documentation Structure
Core Implementation
- [
coding-guidelines.md] - TypeScript and Next.js standards - [
business-logic.md] - Domain-specific business rules - [
monitoring.md] - Error tracking and performance monitoring - [
common-patterns.md] - Reusable code patterns
Development Workflow
- [
feature-development.md] - PRFAQ → PRD → Implementation → GTM workflow - [
project/features/] - Feature templates and documentation- [
001-template/] - Master templates (PRFAQ, PRD, GTM, IMPLEMENTATION) - [
002-feature-name/] - Feature implementation examples - [
00X-feature-name/] - Your features (copy from template)
- [
🚀 Development Commands
Environment Setup
# Install dependencies
npm install
# Start development servers
npm run dev # Main app (port 3000)
npm run dev:admin # Admin dashboard (port 3001) [if applicable]
Database Management
# Generate types
npm run generate-types
# Run migrations
npm run migrate
# Reset database
npm run reset-db
Monitoring & Debugging
# Check monitoring integration
npm run monitor:check
# View logs
npm run logs
# Performance analysis
npm run analyze
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 · 284 lines · 1,983 tokens per session scan A ced0b35f7e6d
project-context is a cursor rule published in the GitHub repository smeubank/cursor-template (6 stars, last pushed 1y ago), licensed MIT. It adds 1,983 tokens to every session, about $0.0079 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.