Borrowing it
Nothing to install: this file belongs to Hackbyrd/orbital-express. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Hackbyrd/orbital-express/main/.claude/skills/setup-and-ops/SKILL.mdgit clone --depth 1 https://github.com/Hackbyrd/orbital-expressWrote 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.
[](https://agentmods.dev/skills/hackbyrd/orbital-express/setup-and-ops)<a href="https://agentmods.dev/skills/hackbyrd/orbital-express/setup-and-ops"><img src="https://agentmods.dev/badge/skills/hackbyrd/orbital-express/setup-and-ops/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.
<a href="https://agentmods.dev/skills/hackbyrd/orbital-express/setup-and-ops"><img src="https://agentmods.dev/badge/skills/hackbyrd/orbital-express/setup-and-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00068 | $0.01405 |
| Opus 5.5 | $0.00027 | $0.00562 |
| Sonnet 5.5 | $0.00014 | $0.00281 |
| Haiku 4.5 | $0.00007 | $0.00140 |
Grade B, and why
setup-and-ops scanned grade B with 1 finding 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 2mo 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Mac: `brew install redis`. Windows: install via WSL2 (`sudo apt-get install redis-server`). Linux: `sudo apt-get install redis-server`. How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup & operations
Operational reference for running and deploying the app. (For building features, use the build skills.) Read README "Before You Begin", "The Entry Points", "Config Folder", "Database Folder", "Deploying to Heroku". Full command cheat sheet, health probes, ngrok details, and troubleshooting table: docs/reference/operations.md.
Prerequisites
- Node v22.x, Yarn. PostgreSQL running locally. Redis installed on the machine (see below). Both Postgres + Redis are required for the app and the test suite.
Redis (installed on your machine)
Redis is installed system-wide — there is no project-local redis/ folder anymore (older versions built Redis inside the repo; that approach is deprecated — delete any leftover redis/ folder).
- Mac:
brew install redis. Windows: install via WSL2 (sudo apt-get install redis-server). Linux:sudo apt-get install redis-server. - Manage the service via yarn (wraps
brew services):yarn redis/yarn redis:start(start),yarn redis:restart,yarn redis:stop,yarn redis:status,yarn redis:logs,yarn redis:info,yarn redis:edit,yarn redis:cleanup,yarn redis:reset. Full steps:docs/redis.txt.
Local dev only. The locally installed Redis is just for your machine. Production uses a managed Redis add-on (Heroku Redis / Redis Cloud) reached via the
REDIS_URLconfig var.
First-time setup
yarn install— installs deps and runspostinstall→yarn lang(compileslocales/). Pin exact versions when adding deps:yarn add <pkg> --exact.- Create env files in
config/from the template: copy.env.template→.env.development,.env.test(and.env.production/.env.stagingonly if connecting to prod locally). These are gitignored. Every new env var → also add it to.env.template(committed).- Required for auth:
ACCESS_TOKEN_SECRET,REFRESH_TOKEN_SECRET(distinct),ACCESS_TOKEN_EXPIRES_IN=15m,REFRESH_TOKEN_EXPIRES_IN=60d— in every env file incl..env.test.
- Required for auth:
- Create the dev DB, run migrations:
yarn migrate. Optionallyyarn seedfor dev seed data.
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.
- 2mo ago First seen · 58 lines · 68 tokens per session scan B eb3e0ccbe080
setup-and-ops is a skill published in the GitHub repository Hackbyrd/orbital-express (15 stars, last pushed 2mo ago), licensed MIT. It adds 68 tokens to every session and 1,405 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
haven-db
Reset, reseed, locate and prune a haven stack's databases with haven db, and know which verbs destroy data. Use when someone says 'haven db', 'reset the database', 'drop the database', 'reseed in place', 'db preset', 'demo preset', 'database url', 'connection string for postgres', 'haven db prune', 'haven seed'…
nw-database-technology-selection
Database comparison catalogs, RDBMS vs NoSQL selection criteria, CAP/ACID/BASE theory, OLTP vs OLAP, and technology-specific characteristics.
vercel-storage
Vercel storage expert guidance — Blob, Global Config (formerly Edge Config), and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.
quarry
Query PostgreSQL, MySQL, Redis and Neptune with Quarry (qy), compare data across environments, maintain reusable queries, and manage connections or the database workbench. Use for database evidence or explicit Quarry tasks, not general database design discussions.
query
Query optimization and EXPLAIN analysis.
vercel-storage
Vercel storage expert guidance — Blob, Edge Config, and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.