orbital-express copilot-instructions.md

Project rules for Orbital Express, an opinionated Express.js and Sequelize framework, covering file generation, feature layout, HTTP behavior, and naming.

In plain words
What is it for?
Use them when adding or changing features, routes, actions, background tasks, tests, and API responses in an Orbital Express project.
Why use it?
They prevent code from drifting away from the framework's required structure and conventions, including rules such as using generators instead of creating feature files by hand.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/hackbyrd/orbital-express/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/Hackbyrd/orbital-express

Made for: GitHub Copilot.

Per session 788 This file is loaded in full into every session.
When invoked 788 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00788 $0.00788
Opus 5 $0.00394 $0.00394
Sonnet 5 $0.00158 $0.00158
Haiku 4.5 $0.00079 $0.00079

Measured 2d ago against content hash 5b1934d1b4c9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

orbital-express 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 2d 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 · 91 lines

How it starts

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

GitHub Copilot Instructions — Orbital Express

This project uses Orbital Express, an opinionated Express.js + Sequelize framework. Full conventions are in AGENTS.md. The rules below are non-negotiable.

Never hand-create feature files

Use the generator for everything:

yarn gen Feature              # full feature scaffold
yarn gen Feature -a V1Action  # add an action
yarn gen Feature -t V1Task    # add a background task
yarn del Feature -a V1Action  # remove generated files (never use rm)

Feature-folder structure

Every feature lives in app/<FeatureName>/. One folder = everything for that feature: model, routes, actions, tasks, tests, languages, mailers.

HTTP conventions

  • POST and GET only — no PUT, PATCH, DELETE
  • Use req.args — never req.body or req.query
  • Responses are flat: { status, success: true, ...payload } — no data wrapper
  • Status codes: 200 default, 201 on create, 202 on background-job handoff
  • Route URLs are lowercase, no separators (/v1/users/logoutall not /v1/users/logout-all)

Naming

  • Actions: V{version}{Action}[By{Role}][On{Device}] (e.g. V1CreateOrder, V1ListOrdersByAdmin)
  • Tasks: same as actions + Task suffix (e.g. V1CreateOrderTask)
  • Feature folders: singular PascalCase (Order, not Orders)
  • Constants: UPPER_CASE — defined in helpers/constants.js, never inline magic strings
  • Booleans: is/has/can/does prefix (e.g. isActive, hasAccess)
  • FK columns: <entity>Id camelCase (e.g. userId, orderId)

Errors

  • HTTP actions: return errorResponse(req, ERROR_CODES.X, ...)
  • Tasks and socket actions: throw new Error(...)
  • Never res.status(500).json(...) — let middleware/error.js handle it

Models

  • UUID v7 primary keys
  • paranoid: true on every model (soft-delete via deletedAt)
  • Always index foreign keys
  • Named indexes: {Table}_{col}_{idx|unique}

Tests

  • Every action has an integration test in app/<Feature>/tests/integration/
  • Every task has a test in app/<Feature>/tests/tasks/
  • Every ERROR_CODE in the action's JSDoc has a test case
  • Always test who cannot do something (unauthorized, wrong role, wrong state)
  • Run with yarn test (uses --runInBand; requires Postgres + Redis)

Read the full file on GitHub · 91 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.

  1. 2d ago First seen · 91 lines · 788 tokens per session scan A 5b1934d1b4c9

Subscribe to this mod's changes

orbital-express copilot-instructions.md is an instructions file published in the GitHub repository Hackbyrd/orbital-express (14 stars, last pushed 13d ago), licensed MIT. It adds 788 tokens to every session, about $0.0039 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.

Related

Other instructions, from other repositories

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens