What is rocketride-server copilot-instructions.md?

Project instructions for RocketRide, an AI pipeline builder used for document processing, retrieval systems, and data integration. They tell an agent which documentation to read before writing Python or TypeScript code.

Use them when creating or changing RocketRide pipelines, configuring components, using its Python or TypeScript SDK, or reading runtime traces.

They reduce errors caused by skipping required setup, pipeline rules, API details, or known pitfalls.

How rocketride-org/rocketride-server configures GitHub Copilot

About the project

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.

rocketride-org/rocketride-server · 19,948 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to rocketride-org/rocketride-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/rocketride-org/rocketride-server/develop/.github/copilot-instructions.md

Clone the repo

git clone --depth 1 https://github.com/rocketride-org/rocketride-server

Made for: GitHub Copilot.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/rocketride-org/rocketride-server/copilot-instructions/github.svg)](https://agentmods.dev/instructions/rocketride-org/rocketride-server/copilot-instructions)

Your own site

<a href="https://agentmods.dev/instructions/rocketride-org/rocketride-server/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/rocketride-org/rocketride-server/copilot-instructions/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/rocketride-org/rocketride-server/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/rocketride-org/rocketride-server/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 808 This file is loaded in full into every session.

When invoked 808 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00808	$0.00808
Opus 5.5	$0.00323	$0.00323
Sonnet 5.5	$0.00162	$0.00162
Haiku 4.5	$0.00081	$0.00081

Measured 1mo ago against content hash a3ee7fa2ce51, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

rocketride-server copilot-instructions.md 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.

.github/copilot-instructions.md · 37 lines

How it starts

The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.

RocketRide: AI Pipeline & App Platform

Use RocketRide when building AI pipelines (document processing, RAG, agents, data integration) or when building apps on the RocketRide platform (React UIs on the platform shell, often embedding pipelines).

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: the platform map, setup, task router
ROCKETRIDE_CLI.md	The `rocketride` command: validate, start/upload runs, store, deploy, app verbs; when to prefer it over SDK code
ROCKETRIDE_CONCEPTS.md	Early, always: workspace, connection, deploy/publish lifecycle, how apps and pipelines fit together
ROCKETRIDE_PIPELINES.md	Writing or editing a `.pipe`: format, lanes, profiles, patterns, pitfalls
ROCKETRIDE_COMPONENT_REFERENCE.md	Choosing/configuring pipeline components via the catalog + schemas
ROCKETRIDE_APPS.md	Building or modifying an app: App Builder, shell UI, manifest, deploy/publish
ROCKETRIDE_UI_COMPONENTS.md	Using a specific UI component in an app: props, wiring, snippets
ROCKETRIDE_INTEGRATIONS.md	MCP tools, n8n, external webhooks, Telegram, mid-pipeline HTTP, CI
ROCKETRIDE_python_API.md	Python SDK: client methods, deploy & schedules, file store, events
ROCKETRIDE_typescript_API.md	TypeScript SDK: client methods, app-sdk, deploy & schedules, events
ROCKETRIDE_OBSERVABILITY.md	Consuming runtime events and logs, building monitoring

Before writing ANY RocketRide code

Read .rocketride/docs/ROCKETRIDE_README.md and follow its task router for the job at hand
Building a pipeline: ROCKETRIDE_CONCEPTS.md + ROCKETRIDE_PIPELINES.md + ROCKETRIDE_COMPONENT_REFERENCE.md
Building an app: ROCKETRIDE_CONCEPTS.md + ROCKETRIDE_APPS.md + ROCKETRIDE_UI_COMPONENTS.md
Driving either from code: NEVER invent anything — verify client.* method names and signatures against your language's API doc (ROCKETRIDE_python_API.md / ROCKETRIDE_typescript_API.md), and pipeline component names and config fields against .rocketride/services-catalog.json and .rocketride/schema/
Two connections may exist in .env: ROCKETRIDE_URI/ROCKETRIDE_APIKEY (development - run/validate/iterate) and ROCKETRIDE_DEPLOY_URI/ROCKETRIDE_DEPLOY_APIKEY (deployment target - deploy/publish/schedule). Never run lifecycle verbs against the dev pair; if the DEPLOY pair is absent, no deploy target is configured - ask the user.
NEW apps are created ONLY through the scaffold - agents call client.deploy.createApp(slug, ...) (install the client first from the workspace's own .rocketride/client/rocketride.tgz - the scaffold vendors it from the connected server, so it is present once the workspace has been opened against one; with no server URL known the scaffold skips vendoring and the tarball lands on the next connected open - NEVER from the npm registry); humans use the App Builder's New App wizard. Never hand-create app files. (For lifecycle operations generally, prefer the rocketride command; see ROCKETRIDE_CLI.md.)

Read the full file on GitHub · 37 lines

Changes

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 Changed · +3 lines · +357 tokens per session a3ee7fa2ce51
1mo ago Changed · +3 lines · +80 tokens per session 60f00cd9c82d
1mo ago First seen · 31 lines · 371 tokens per session scan A 255584f5523a

Subscribe to this mod's changes

rocketride-server copilot-instructions.md is an instructions file published in the GitHub repository rocketride-org/rocketride-server (19,948 stars, last pushed today), licensed MIT. It adds 808 tokens to every session, about $0.0032 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-10.

C and C++Data Processing Data and AI RAG and vectors ai data-pipeline machine-learning mcp

rocketride-server copilot-instructions.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
rocketride-server copilot-instructions.mdrocketride-org/rocketride-server	Instructions file	20k	today	MIT	A	808	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

rocketride-server: Instructions file for GitHub Copilot