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 skills/hackbyrd/orbital-express/sync-docsnpx skills add Hackbyrd/orbital-express --skill sync-docsgit clone --depth 1 https://github.com/Hackbyrd/orbital-expressWhat 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.00079 | $0.01473 |
| Opus 5 | $0.00039 | $0.00737 |
| Sonnet 5 | $0.00016 | $0.00295 |
| Haiku 4.5 | $0.00008 | $0.00147 |
Grade A, and why
sync-docs 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Keep the documentation in sync
This project documents the same conventions in several places, for different audiences. They must agree. Whenever you change one, you are responsible for propagating the change to every other surface that covers the same thing — in the same unit of work, not "later." A convention that says one thing in the README and another in a skill is worse than no docs.
The documentation surfaces (the canonical set)
| Surface | Audience / purpose |
|---|---|
documentation.html |
The big Stripe-style single-page onboarding site for humans. Deep, narrative, examples. |
README.md |
The full human onboarding doc in the repo. Deep explanations, kept in sync with documentation.html. |
docs/conventions.txt |
The terse, authoritative rulebook. When rules conflict, this wins — so it must always reflect the decision. |
AGENTS.md |
Canonical, tool-agnostic agent guide (Cursor/Codex/Copilot read this directly). Golden rules + skill index. |
CLAUDE.md |
Claude Code entry point — imports AGENTS.md; Claude-specific notes only. |
.claude/skills/*/SKILL.md |
Step-by-step playbooks an agent executes. The operational form of the conventions. |
database/schema.sql |
Documentation of every table (column-order / naming template at top). |
docs/*.md, docs/*.txt |
Topic docs (auth-migration, workflow, etc.). |
mcp/content/ + generated MCP bundle |
Downstream packaged framework knowledge. Regenerate with the repository's MCP bundler and verify no source/bundle drift whenever canonical docs or skills change. |
create-orbital-app templates (sibling repository) |
Downstream starter copies of framework files/docs/skills. Sync intentionally and run its template drift verification whenever canonical framework surfaces change. |
The rule
Editing one documentation surface is not complete until you have checked every other surface for the same content and updated the ones that need it.
This applies in both directions: change the README → check the HTML, conventions, AGENTS, and the relevant skill(s). Change a skill → check whether the rule it encodes also lives in the README/HTML/conventions/AGENTS. Etc.
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.
- 2d ago First seen · 60 lines · 79 tokens per session scan A 91b810a14cd5
sync-docs is a skill published in the GitHub repository Hackbyrd/orbital-express (14 stars, last pushed 13d ago), licensed MIT. It adds 79 tokens to every session and 1,473 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…