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/reliverse/experiments/web-app-documentationgit clone --depth 1 https://github.com/reliverse/experimentsWhat 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.01042 |
| Opus 5 | $0.00000 | $0.00521 |
| Sonnet 5 | $0.00000 | $0.00208 |
| Haiku 4.5 | $0.00000 | $0.00104 |
Grade A, and why
web-app-documentation 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 today.
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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web App and Documentation Patterns
Guidelines for working with the Next.js documentation website in apps/web/.
Next.js App Structure
- Uses Next.js 15+ with App Router
- Documentation content in apps/web/content/docs/
- Landing page components in apps/web/components/landing/
- UI components using shadcn/ui in apps/web/components/ui/
Documentation Content
- MDX files with frontmatter in content/docs/
- Meta files for navigation: meta.json
- API documentation in content/docs/api/
- Plugin documentation in content/docs/core-concepts/plugins.mdx
- Package docs for plugins in content/docs/packages/plugins/
- Examples and guides in respective subdirectories
File Naming in Web App
- Use kebab-case for components:
code-comparison.tsx,features-grid.tsx - Page files follow Next.js conventions:
page.tsx,layout.tsx - Keep component files focused and modular
Landing Page Components
Key landing page sections in components/landing/:
- hero.tsx - Main hero section
- features-grid.tsx - Feature highlights
- code-comparison.tsx - Code examples
- examples-showcase.tsx - Live examples
- cta-section.tsx - Call-to-action
Styling
- Tailwind CSS for styling
- Custom styles in global.css
- Use CSS variables for theming
- Responsive design patterns throughout
Content Management
- MDX content processed by Fumadocs (see source.config.ts)
- API route for search in app/api/search/route.ts
- Dynamic routing for docs in app/docs/[[...slug]]/page.tsx
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.
- today First seen · 146 lines · 0 tokens per session scan A e6cb88dcb31f
web-app-documentation is a cursor rule published in the GitHub repository reliverse/experiments (118 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,042 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-09-01.
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.