RocketRide is an open-source AI development environment and data-pipeline runtime that lets developers compose, debug, observe, and deploy model-based workflows from an IDE or terminal. Its C++ engine runs portable pipelines with extensible nodes for language models, vector databases, document processing, and agent orchestration on the user's infrastructure. The catalogue entries relate to operating and developing with RocketRide's workflows, SDKs, and tooling.
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 skills add rocketride-org/rocketride-server --skill rocketride-designing-pipelinesgit clone --depth 1 https://github.com/rocketride-org/rocketride-serverWrote 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/skills/rocketride-org/rocketride-server/rocketride-designing-pipelines)<a href="https://agentmods.dev/skills/rocketride-org/rocketride-server/rocketride-designing-pipelines"><img src="https://agentmods.dev/badge/skills/rocketride-org/rocketride-server/rocketride-designing-pipelines/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/skills/rocketride-org/rocketride-server/rocketride-designing-pipelines"><img src="https://agentmods.dev/badge/skills/rocketride-org/rocketride-server/rocketride-designing-pipelines.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.00049 | $0.01835 |
| Opus 5.5 | $0.00020 | $0.00734 |
| Sonnet 5.5 | $0.00010 | $0.00367 |
| Haiku 4.5 | $0.00005 | $0.00184 |
Grade A, and why
rocketride-designing-pipelines 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 1mo 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designing RocketRide Pipelines
Turns a plain-language request into an approved, lane-correct DAG — before any node is
configured. Two outputs, two gates: a node selection (Gate A) and a wired topology (Gate B).
The gate rules and forcing functions are in
../rocketride-building-pipelines/GATE_PROTOCOL.md — they apply here.
You work from the node index (L1): LAYER1_NODE_INDEX.json (bundled), or the live
get_services() / .rocketride/services-catalog.json. Each entry is name · classType · lanes · invoke. The index is enough to select and wire; it carries no config fields (that's Phase 2).
The bundled index is reconciled against this repo's node corpus (nodes/src/nodes/), so it can
drift from the set a particular live engine actually has registered.
The live MCP list_components tool lists names/summaries only (no lanes) and hides nodes whose
integration isn't configured — use it to check availability, but wire from the bundled index +
per-node schemas. If a node you expect is missing from it, check list_integrations first.
Phase 1a — Discover (→ Gate A)
- Restate the task in one line: the input data, the wanted output. ("Input: user questions. Output: answers grounded in uploaded PDFs.")
- Explore archetypes exhaustively. Group the index by
classTypeand walk every archetype that could plausibly contribute. Don't stop at the first match. The archetypes:source(chat/webhook/dropper/filesys/telegram) ·data/parse (parse/llamaparse/reducto/ landing_ai_parse/landing_ai_extract) ·text(extract_data/ner/anonymize_text/dictionary/prompt/summarization) ·preprocessor·image·audio·video·embedding·llm(14 providers) ·store(vector DBs) ·database(db_) ·agent·tool(tool_) ·memory·rerank·search·guard·infrastructure/target/response_*(terminals). For each relevant archetype, list the candidate nodes you see in the index. - Select, citing each:
Found in index: <name> · classType=[…] · lanes={…}. A pipeline needs a resolvable source (one Source-mode node, or several withsourcenaming the one that starts the run, in the file or at launch) and a terminal (response_*for a reply; a store /db_*for ingestion). Pull the right converters from the lane cheat-sheet in../rocketride-building-pipelines/pipeline-patterns.md. - Gate A — end with the count line and the gate:
Archetypes explored (N). Selected nodes (M): <name · role>, … — all cited from the index. Approve these M nodes? (yes / adjust / cancel) Then use the Write tool to write
.context/GATE_STATE.md=GATE A | presented | status: AWAITING(GATE_PROTOCOL §2 — so the gate survives a context reset), and STOP. (See §1.)
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 96 lines · 49 tokens per session scan A 8dd8b7d6e6af
rocketride-designing-pipelines is a skill published in the GitHub repository rocketride-org/rocketride-server (18,814 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 1,835 once invoked, about $0.0002 per session on Opus 5.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-15.
Other skills, from other repositories
hugging-face-model-trainer
This skill should be used when users want to train or fine-tune language models using TRL (Transformer Reinforcement Learning) on Hugging Face Jobs infrastructure. Covers SFT, DPO, GRPO and reward modeling training methods, plus GGUF conversion for local deployment. Includes guidance on the TRL Jobs package, UV…
hugging-face-datasets
Create and manage datasets on Hugging Face Hub. Supports initializing repos, defining configs/system prompts, streaming row updates, and SQL-based dataset querying/transformation. Designed to work alongside HF MCP server for comprehensive dataset workflows.
pysr
Use when fitting equations to data with PySR or SymbolicRegression.jl, when a user wants an interpretable formula, symbolic model, scaling law, or empirical relation discovered from numeric data, or when debugging a PySR search that is slow, stuck, or giving poor equations.
trulens-evaluation-setup
Configure feedback functions and selectors for TruLens evaluations.
trulens-instrumentation
Instrument LLM apps with TruLens OTEL-based tracing - from setup to debugging and optimization.
ax-cpp-gen
Use when writing C++ code with axllm for AxGen programs, forward calls, indexed multi-sampling, result pickers, streaming, tools, assertions, traces, usage, and output parsing.