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/write-tests/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/write-tests)<a href="https://agentmods.dev/skills/hackbyrd/orbital-express/write-tests"><img src="https://agentmods.dev/badge/skills/hackbyrd/orbital-express/write-tests/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/write-tests"><img src="https://agentmods.dev/badge/skills/hackbyrd/orbital-express/write-tests.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.00066 | $0.01541 |
| Opus 5.5 | $0.00026 | $0.00616 |
| Sonnet 5.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 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.
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.
- 2mo 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 (15 stars, last pushed 2mo ago), licensed MIT. It adds 66 tokens to every session and 1,541 once invoked, about $0.0003 per session on Opus 5.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
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
dart-test
DART Test: unit tests, integration tests, CI validation, and debugging.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.