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/feature-development)<a href="https://agentmods.dev/rules/smeubank/cursor-template/feature-development"><img src="https://agentmods.dev/badge/rules/smeubank/cursor-template/feature-development/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/feature-development"><img src="https://agentmods.dev/badge/rules/smeubank/cursor-template/feature-development.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.00000 | $0.01640 |
| Opus 5.5 | $0.00000 | $0.00656 |
| Sonnet 5.5 | $0.00000 | $0.00328 |
| Haiku 4.5 | $0.00000 | $0.00164 |
Grade A, and why
feature-development 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Development Workflow
🎯 Overview
This project follows a structured feature development process: PRFAQ → PRD → Implementation → GTM. This ensures thoughtful planning, clear requirements, and successful launches.
CRITICAL: Always follow this workflow for ALL new features. Never skip phases or start implementation before completing PRFAQ and PRD.
📂 Template System
Location
.cursor/project/features/
├── 001-template/ # Master templates
│ ├── PRFAQ.md # Problem definition and solution
│ ├── PRD.md # Product requirements document
│ ├── GTM.md # Go-to-market strategy
│ └── IMPLEMENTATION.md # Technical implementation and PR description
├── 002-example-feature/ # EXAMPLE: Completed feature
│ ├── PRFAQ.md # ✅ Problem validation
│ ├── PRD.md # ✅ Technical requirements
│ ├── GTM.md # ✅ Launch strategy
│ └── IMPLEMENTATION.md # ✅ Technical implementation and PR description
├── 003-feature-name/ # Next feature
└── ...
Naming Convention
- Use 3-digit zero-padded numbers:
001,002,003 - Follow with descriptive kebab-case name:
booking-system,contact-form - Example:
002-online-booking-system
Template Files
- PRFAQ.md - Problem definition, customer quotes, goals
- PRD.md - Technical requirements, user stories, success criteria
- GTM.md - Launch strategy, communication plan, success metrics
- IMPLEMENTATION.md - Technical implementation details and PR description
🔄 Development Workflow
Phase 1: Problem Definition (PRFAQ)
Goal: Validate the problem and solution before investing in detailed requirements
Activities:
- Copy template:
cp -r .cursor/project/features/001-template .cursor/project/features/00X-feature-name - Complete PRFAQ.md with problem definition and solution validation
- Include customer quotes and user reactions
- Define qualitative and quantitative goals
- List open questions and assumptions
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 · 204 lines · 0 tokens per session scan A 27224c9524da
feature-development is a cursor rule published in the GitHub repository smeubank/cursor-template (6 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,640 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.
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.