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/oakensoul/nextjs-cursor-promptsWrote 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/oakensoul/nextjs-cursor-prompts/prompt-create)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/prompt-create"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/prompt-create.svg" alt="Measured on agentmods" 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.02779 |
| Opus 5 | $0.00000 | $0.01389 |
| Sonnet 5 | $0.00000 | $0.00556 |
| Haiku 4.5 | $0.00000 | $0.00278 |
Grade A, and why
prompt-create 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 7d 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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt Creation Guide
This prompt guides the creation of new, high-quality prompts that follow established standards and integrate seamlessly with the existing prompt collection.
🎯 PROMPT CREATION OBJECTIVES:
- CREATE standards-compliant prompts following established guidelines
- ENSURE seamless integration with existing prompt collection
- OPTIMIZE for user experience and practical application
- IMPLEMENT best practices from project documentation
- MAINTAIN consistency across the prompt ecosystem
📋 PROMPT CREATION PROCESS:
STEP 1: Requirements Analysis
Define Prompt Purpose:
- Primary objective - What specific problem does this prompt solve?
- Target audience - Who will use this prompt? (developers, AI assistants, etc.)
- Use case scenarios - When and why would someone need this prompt?
- Success criteria - How will you know the prompt is effective?
- Integration points - How does this connect to existing prompts/workflows?
Scope Definition:
- Core functionality - Essential features the prompt must include
- Boundaries - What the prompt should NOT attempt to do
- Prerequisites - What users need before using this prompt
- Dependencies - What other prompts, tools, or knowledge are required
- Edge cases - Unusual scenarios the prompt should handle
Category and Placement:
Determine the appropriate category folder:
- accessibility/ - WCAG compliance and inclusive design
- api/ - API development and integration
- code/ - Code quality, review, and improvement
- component/ - React component development
- deploy/ - Deployment preparation and processes
- git/ - Git workflow and version control
- test/ - Testing strategies and implementation
- prompt-engineering/ - Meta-prompts for prompt development
STEP 2: Standards Integration Planning
Prompt Standards Compliance (docs/standards/standards-prompt.md):
- Naming convention - Follow [category]-[action]-[target].mdc pattern
- Frontmatter structure - Include all required YAML fields
- Content organization - Use established section patterns
- Quality guidelines - Meet clarity, completeness, and usability standards
- Version management - Start with 1.0.0, plan for evolution
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.
- 7d ago First seen · 384 lines · 0 tokens per session scan A ba5de9fa8fdd
prompt-create is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,779 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
baml
A set of rules for setting up BAML and help with syntax guidance.
co-dialectic
Co-Dialectic prompt sharpening and verification rules for Cursor.
prompt-routing
Route tasks to the correct Universal AI Engineering Prompt.
prompting-for-qe
Soạn/tinh chỉnh prompt cho tác vụ QE (sinh test case, phân tích requirement, tóm tắt tài liệu test, phân tích log) — đặc biệt khi output AI lan man, chung chung, bịa, hoặc muốn chốt prompt thành template tái dùng.
llm-zod-jsonschema
Best Practice for LLM Output Parsing with Zod and JSON Schema.
prompt-evals
Prompt eval fixtures — case design, assertions, versioning, CI gates, no PII in golden data.