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/write-testsnpx skills add Hackbyrd/orbital-express --skill write-testsgit 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.00066 | $0.01541 |
| Opus 5 | $0.00033 | $0.00771 |
| Sonnet 5 | $0.00013 | $0.00308 |
| Haiku 4.5 | $0.00007 | $0.00154 |
Grade A, and why
write-tests 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.
Write tests
Tests use Jest + supertest against a real Postgres + Redis (no DB mocks). Read README "Tests Folder", "Writing Testable Code", "Testing: *" sections. Postgres and Redis must be running, and the suite runs --runInBand (parallel suites race on sync({force:true})).
Writing testable code (do this BEFORE testing)
Separate logic from I/O. An action/task does three things: load (DB/API), process (business logic), save (DB/side effects). Extract the process step into a pure function in helper.js (or the global helpers/logic.js) — plain inputs → plain output, no DB, no API, no req. Then:
- Test that pure function exhaustively in
helper.test.js(every edge case — fast, no DB/server/mocks). - Test the action/task integration once (the happy path + error/auth cases) — its only job is to verify wiring (loaded the right record, called the service, wrote the result). Don't re-run every logic edge case through the full HTTP+DB stack.
- If you can't test a piece of logic without a running DB, that's the signal to extract it.
Where tests live (mandatory — never put a test file anywhere else)
app/<Feature>/tests/integration/V1<Action>.test.js— one per action (full HTTP via supertest).app/<Feature>/tests/tasks/V1<Task>.test.js— one per task (call the task fn directly, assert side effects).app/<Feature>/tests/helper.test.js— pure unit tests forapp/<Feature>/helper.js(no server/DB).test/helpers/<name>.test.js— pure unit tests for files inhelpers/<name>.js.test/services/<name>.test.js— pure unit tests for files inservices/<name>.js.
Never drop a test directly in test/ — every test file lives in a sub-folder that mirrors where its source lives. A test for services/email.js goes in test/services/email.test.js; a test for helpers/logic.js goes in test/helpers/logic.test.js.
Every feature retains tests/helper.test.js, tests/integration/, and tests/tasks/; empty integration/task directories use README markers. Restore missing counterparts with yarn repair <Feature> --dry-run, review, then yarn repair <Feature>. Repair never overwrites.
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 · 66 tokens per session scan A 247ab2683846
write-tests is a skill published in the GitHub repository Hackbyrd/orbital-express (14 stars, last pushed 13d ago), licensed MIT. It adds 66 tokens to every session and 1,541 once invoked, about $0.0003 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…