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/architecture)<a href="https://agentmods.dev/rules/smeubank/cursor-template/architecture"><img src="https://agentmods.dev/badge/rules/smeubank/cursor-template/architecture/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/architecture"><img src="https://agentmods.dev/badge/rules/smeubank/cursor-template/architecture.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.01317 | $0.01317 |
| Opus 5.5 | $0.00527 | $0.00527 |
| Sonnet 5.5 | $0.00263 | $0.00263 |
| Haiku 4.5 | $0.00132 | $0.00132 |
Grade A, and why
architecture 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Architecture
🏗️ Repository Structure
project-template/
├── .cursor/ # AI assistant configuration
│ ├── rules/ # Core rules and patterns
│ └── project/ # Project-specific documentation
├── app/ # Next.js App Router application
│ ├── (public)/ # Public routes
│ ├── (admin)/ # Admin routes [if applicable]
│ ├── api/ # API routes
│ ├── globals.css # Global styles
│ └── layout.tsx # Root layout
├── components/ # Reusable UI components
│ ├── ui/ # Base UI components (ShadCN/UI)
│ └── business/ # Domain-specific components
├── lib/ # Utility functions and configurations
│ ├── database.ts # Database client configuration
│ ├── auth.ts # Authentication utilities
│ ├── validation.ts # Form validation schemas
│ └── utils.ts # General utilities
├── types/ # TypeScript type definitions
├── public/ # Static assets
└── docs/ # Additional documentation
🎯 Design Principles
Separation of Concerns
- App Router for routing and page structure
- Components for reusable UI elements
- Lib for business logic and utilities
- Types for TypeScript definitions
Performance First
- Server Components by default
- Client Components only when necessary
- Image optimization with Next.js
- Tailwind CSS with custom brand color palette
- Code splitting and lazy loading
Monitoring & Observability
- Sentry for error tracking and performance monitoring
- Structured logging throughout the application
- User journey tracking and analytics
🏢 Application Architecture
Customer Site (/app)
Purpose: Main user-facing application Technology: Next.js 15 App Router Port: 3000
Key Features:
- Public pages and user interface
- User authentication and profiles
- Business functionality (booking, contact, etc.)
- Responsive design for all devices
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 · 187 lines · 1,317 tokens per session scan A 4abe75289e97
architecture is a cursor rule published in the GitHub repository smeubank/cursor-template (6 stars, last pushed 1y ago), licensed MIT. It adds 1,317 tokens to every session, about $0.0053 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.