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.
npx agentmods add rules/oakensoul/nextjs-cursor-prompts/documentation-create-llmsgit 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/documentation-create-llms)<a href="https://agentmods.dev/rules/oakensoul/nextjs-cursor-prompts/documentation-create-llms"><img src="https://agentmods.dev/badge/rules/oakensoul/nextjs-cursor-prompts/documentation-create-llms.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 | $0.00000 | $0.02290 |
| Opus 5 | $0.00000 | $0.01145 |
| Sonnet 5 | $0.00000 | $0.00458 |
| Haiku 4.5 | $0.00000 | $0.00229 |
Grade A, and why
documentation-create-llms 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 5d 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM Developer Guide Creation
This prompt creates comprehensive llms.md documentation that serves as a technical overview and integration guide for LLM developers working with AI-assisted development frameworks.
🎯 OBJECTIVES:
- CREATE comprehensive project overview tailored for LLM developers and AI assistants
- DOCUMENT AI assistance architecture including prompts, rules, and standards
- PROVIDE technical integration patterns and usage examples
- ESTABLISH quality standards for AI-assisted development
- ENABLE effective LLM collaboration through clear documentation
📋 LLM GUIDE CREATION PROCESS:
STEP 1: Project Architecture Analysis
Repository Structure Assessment:
# Analyze the complete project structure
echo "🔍 Repository Structure Analysis"
echo "================================"
# Core directories to document
- .cursor/ # AI assistance infrastructure
- prompts/ # Task-specific prompts
- rules/ # Cross-cutting constraints
- docs/standards/ # Development standards
- examples/ # Usage examples
- templates/ # Code templates
- scripts/ # Automation tools
# Count and categorize prompts
find .cursor/prompts -name "*.mdc" | wc -l
find .cursor/rules -name "*.mdc" | wc -l
# Identify prompt categories and specializations
ls .cursor/prompts/*/
Technology Stack Documentation:
- Framework and versions - Core technologies and their versions
- Testing infrastructure - Testing frameworks and strategies
- Development tools - Build tools, linters, formatters
- Integration patterns - How different technologies work together
- Deployment targets - Production environment specifications
Standards Integration:
- Coding standards integration and enforcement
- Testing standards and coverage requirements
- Architecture patterns and design principles
- Quality gates and validation processes
- Security requirements and compliance standards
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.
- 5d ago First seen · 295 lines · 0 tokens per session scan A 76a9387b002f
documentation-create-llms 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,290 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
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.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.