orbital-express CLAUDE.md

Project instructions for Claude Code in the Orbital-Express repository, alongside the main AGENTS.md rules. They explain where skills, nested instructions, settings and documentation-sync checks are kept.

In plain words
What is it for?
Use them when Claude Code works on Orbital-Express, especially when changing application code, skills, settings or documentation.
Why use it?
They help Claude Code load the right repository guidance and keep related documentation consistent after changes.

Instructions file

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/claude-md
Clone the repo
git clone --depth 1 https://github.com/Hackbyrd/orbital-express
Per session 311 This file is loaded in full into every session.
When invoked 311 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.00311 $0.00311
Opus 5 $0.00156 $0.00156
Sonnet 5 $0.00062 $0.00062
Haiku 4.5 $0.00031 $0.00031

Measured 2d ago against content hash 76d4f3f43d6a, 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 CLAUDE.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.

CLAUDE.md · 14 lines

What it actually says

CLAUDE.md

This project's agent guide is AGENTS.md (tool-agnostic, canonical). Read it — it's imported below.

@AGENTS.md

Claude Code specifics

  • Skills live in .claude/skills/. They auto-invoke when a task matches their description, or run them explicitly (e.g. /create-feature). Prefer the skill for any task it covers.
  • Nested context: app/CLAUDE.md (if present) loads automatically when you work inside app/. Keep deep, area-specific notes there rather than bloating this file.
  • Full rulebook: docs/conventions.txt is the authoritative, detailed rules — read it on demand for anything ambiguous; AGENTS.md summarizes the non-negotiables.
  • Personal settings go in .claude/settings.local.json (gitignored). Shared, committed settings go in .claude/settings.json.
  • Docs stay in sync (enforced): a committed PostToolUse hook (.claude/hooks/doc-sync-reminder.py, wired in .claude/settings.json) fires whenever you edit any documentation surface (documentation.html, README.md, docs/*, AGENTS.md, CLAUDE.md, database/schema.sql, any SKILL.md) and reminds you to reconcile the others. Follow the sync-docs skill — a doc change isn't done until the parallel surfaces and the relevant skill(s) agree.
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 · 14 lines · 311 tokens per session scan A 76d4f3f43d6a

Subscribe to this mod's changes

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

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

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

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