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/project-context)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/project-context"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/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/oakensoul/nextjs-cursor-prompts/project-context"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/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.00032 | $0.01108 |
| Opus 5 | $0.00016 | $0.00554 |
| Sonnet 5 | $0.00006 | $0.00222 |
| Haiku 4.5 | $0.00003 | $0.00111 |
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 6d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Context Reference Rule
When you lack sufficient context about this project's structure, patterns, conventions, or development practices, consult the project documentation in LLMs.mdc for comprehensive guidance.
🎯 RULE OBJECTIVES:
- ENSURE comprehensive understanding of project context before making changes
- PREVENT assumptions about project structure and conventions
- MAINTAIN consistency with established project practices
- REDUCE errors from insufficient background knowledge
- ACCELERATE onboarding to project-specific patterns
🔍 WHEN TO APPLY THIS RULE:
Context Insufficiency Indicators:
- Unfamiliar with project architecture or file organization
- Unclear about coding standards or conventions used
- Uncertain about testing patterns or requirements
- Don't understand deployment or development workflow
- Need background on project scope and objectives
- Unsure about dependencies or technology stack decisions
- Lack understanding of existing component patterns
- Need clarity on API design principles
- Uncertain about database schema or data patterns
Mandatory Consultation Scenarios:
- First time working with this codebase
- Complex refactoring or architectural changes
- Integration work with existing systems
- New feature development that touches multiple areas
- Performance optimization requiring system understanding
- Security implementations needing context about data flow
- API changes affecting multiple consumers
📋 CONSULTATION PROCESS:
STEP 1: Context Assessment
Before starting any significant work:
- Evaluate current understanding of the project
- Identify knowledge gaps that could affect the task
- Determine consultation necessity based on task complexity
STEP 2: Documentation Review
When context is insufficient:
- Read LLMs.mdc thoroughly for project overview
- Focus on sections relevant to your current task
- Note key patterns and conventions to follow
- Understand constraints and architectural decisions
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.
- 6d ago First seen · 130 lines · 32 tokens per session scan A 959ee6eb5ed3
project-context is a cursor rule published in the GitHub repository oakensoul/nextjs-cursor-prompts (4 stars, last pushed 1y ago), licensed MIT. It adds 32 tokens to every session and 1,108 once invoked, about $0.0002 per session on Opus 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-09-03.
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.
cli-error-handling
CLI command error handling patterns.
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.