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/rocketride-org/rocketride-server/cursorgit clone --depth 1 https://github.com/rocketride-org/rocketride-serverWhat 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.00397 |
| Opus 5 | $0.00000 | $0.00198 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
cursor 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 yesterday.
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.
What it actually says
RocketRide — AI Pipeline Builder
Use RocketRide when building AI pipelines, document processing, RAG systems, or data integration.
Documentation
Full docs: .rocketride/docs/
Read the relevant doc(s) before generating any RocketRide code.
| File | Read when... |
|---|---|
| ROCKETRIDE_README.md | Starting any RocketRide work — overview + mandatory setup steps |
| ROCKETRIDE_QUICKSTART.md | Writing first pipeline — complete working examples (Python & TS) |
| ROCKETRIDE_PIPELINE_RULES.md | Defining pipelines — structure, lane wiring, config rules |
| ROCKETRIDE_COMPONENT_REFERENCE.md | Choosing/configuring components — all providers and config fields |
| ROCKETRIDE_COMMON_MISTAKES.md | Before finalizing — known pitfalls to avoid |
| ROCKETRIDE_python_API.md | Python SDK — client methods, types, patterns |
| ROCKETRIDE_typescript_API.md | TypeScript SDK — client methods, types, patterns |
| ROCKETRIDE_OBSERVABILITY.md | Consuming runtime logs, lifecycle events, and pipeline traces |
Before Writing ANY RocketRide Code
- Read
.rocketride/docs/ROCKETRIDE_README.mdfor mandatory setup requirements - Read the relevant API doc (Python or TypeScript) for your language
- Read
.rocketride/docs/ROCKETRIDE_PIPELINE_RULES.md+.rocketride/docs/ROCKETRIDE_COMPONENT_REFERENCE.md - Read
.rocketride/docs/ROCKETRIDE_COMMON_MISTAKES.mdbefore finalizing
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.
- yesterday First seen · 34 lines · 0 tokens per session scan A b683c745fef3
cursor is a cursor rule published in the GitHub repository rocketride-org/rocketride-server (7,496 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 397 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-30.
Other cursor rules, from other repositories
python_tests
We use the unit tests to cover internal behavior that can work without the web / backend counterpart. We aim for 95%+ unit test coverage of our Python code in lib/streamlit.
scripts
Utility scripts for development and CI/CD.
zenml-domain-models
How to understand, add or modify ZenML domain models.
mod-000a-reusable-layers-belong-in-nn
Reusable layers and building blocks should be placed in physicsnemo/nn, not physicsnemo/models. Examples include FullyConnected, attention layers, and UNetBlock.
mod-003c-missing-required-class-docstring-sections
Class docstrings must contain three mandatory sections - Parameters, Forward, and Outputs. Optional sections include Notes, Examples, ..important::, and ..code-block::.
mod-003f-callback-functions-must-have-code-block-specification
Callback function parameters must include a ..code-block:: specification showing the required signature and return type, placed outside Parameters/Forward/Outputs sections.