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 instructions/rocketride-org/rocketride-server/agents-mdgit 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.00383 | $0.00383 |
| Opus 5 | $0.00192 | $0.00192 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
rocketride-server AGENTS.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 3d 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.
What it actually says
AGENTS.md
Contributor guide for agents working in this repository.
Co-located documentation rule
Documentation is co-located with the code it documents and is gathered into the
docs site by builder docs:build. When a change alters a public contract, update
the corresponding co-located doc in the SAME change:
- A node's inputs, outputs, or config schema -> prose in
nodes/src/nodes/<name>/README.md. Never hand-edit content between<!-- ROCKETRIDE:GENERATED:PARAMS START -->and<!-- ROCKETRIDE:GENERATED:PARAMS END -->; it is regenerated fromservices*.jsonbynodes:docs-generate. - A public TypeScript SDK signature ->
packages/client-typescript/docs/. Reference underdocs/reference/is generated byclient-typescript:docs-generate(do not edit). - A public Python SDK signature ->
packages/client-python/docs/(reference generated). - The MCP protocol surface ->
packages/client-mcp/docs/. - The WebSocket (5565) / engine protocol surface ->
packages/server/docs/. - The
.pipeschema (packages/client-typescript/src/client/types/pipeline.ts) -> its reference regenerates to/pipeline-reference. - The VS Code extension surface ->
apps/vscode/docs/. - Spine/landing pages (Home, Quickstart, Concepts, Cloud, Troubleshooting, Glossary,
Cursor/Windsurf stubs) ->
packages/docs/content-static/.
Prose-only edits and internal refactors that do not change a public contract do not
require doc updates. Treat the doc as part of the change, not a follow-up. Do not create
a separate docs repo or a top-level docs site folder. Verify with builder docs:build.
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.
- 3d ago First seen · 29 lines · 383 tokens per session scan A 13e5df95c968
rocketride-server AGENTS.md is an instructions file published in the GitHub repository rocketride-org/rocketride-server (7,634 stars, last pushed yesterday), licensed MIT. It adds 383 tokens to every session, about $0.0019 per session on Opus 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-08-30.
Other instructions, from other repositories
marimo AGENTS.md
Instructions for marimo-team/marimo, covering marimo development guidelines, your primary responsibility is to the project and its users, quick setup, development commands and python.
streamlit copilot-instructions.md
Copilot instructions for streamlit/streamlit, covering streamlit repo overview, tech stack, folder structure, shell & build policy and make commands.
gradio AGENTS.md
AGENTS.md instructions for gradio-app/gradio, covering agents.md, repository structure, pull request rules, code style and agentic contribution policy.
mlflow code-review.instructions.md
Instructions for mlflow/mlflow, covering code review instructions, knowledge cutoff and do not comment on.
marimo copilot-instructions.md
Instructions for marimo-team/marimo: For example, if there is a frontend change to make a border thicker, how does this look in run mode, app-view and edit-view? For a backend change, has the user tested different scenarios?
zenml AGENTS.md
AGENTS.md instructions for zenml-io/zenml, covering zenml codex agent guidelines, project structure, always-loaded rules, common commands and branches, git, and prs.