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/examples-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.00915 |
| Opus 5 | $0.00000 | $0.00458 |
| Sonnet 5 | $0.00000 | $0.00183 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
examples-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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Examples Documentation Strategy
Rempts has a comprehensive examples system with dual documentation approaches for different audiences.
Examples Structure
The examples/ directory contains 6 examples organized in learning progression:
- minimal/ - Single command, basic setup (starting point)
- schema-validation/ - Type-safe validation with Zod
- command-structure/ - Multi-command organization
- interactive/ - Prompts, wizards, user interaction
- real-world/ - Production-ready patterns and best practices
- plugin-example/ - Plugin development with type-safe stores
Dual Documentation Approach
Repository Documentation
- examples/README.md - 172 lines covering all examples, key concepts, build patterns
- Individual READMEs - Each example has detailed README with usage, concepts, and features demonstrated
- Runnable code - All examples can be run with
bun installandbun cli.ts
Web Documentation
- apps/web/content/docs/examples/index.mdx - Landing page
- Detailed tutorials - Each example has comprehensive MDX documentation:
- minimal.mdx - 213 lines
- interactive.mdx - 505 lines
- multi-command.mdx - 591 lines
- real-world.mdx - 632 lines
Working with Examples
For Learning
Follow the progression path:
- Start with minimal to understand basics
- Move to schema-validation for type safety
- Explore command-structure for organization
- Try interactive for user experience
- Study real-world for production patterns
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 · 103 lines · 0 tokens per session scan A 44772b685105
examples-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 915 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.