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/add-fixtures/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/add-fixtures)<a href="https://agentmods.dev/skills/hackbyrd/orbital-express/add-fixtures"><img src="https://agentmods.dev/badge/skills/hackbyrd/orbital-express/add-fixtures.svg" alt="Measured on agentmods" 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.00054 | $0.00693 |
| Opus 5 | $0.00027 | $0.00347 |
| Sonnet 5 | $0.00011 | $0.00139 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
add-fixtures 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 7d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add fixtures (test data) and seed data (dev data)
Two parallel datasets: fixtures load into the test DB (test/fixtures/), seed loads into the dev DB (database/seed/). Both mirror the table structure. Read README "fixtures" and "The Seed Data via seed folder".
For feature/schema changes, include fixture topology and sequence placement in the approved plan before editing. Confirm the feature has complete standard structure with yarn repair <Feature> --dry-run, then yarn repair <Feature>; do not hand-create missing feature scaffolding.
Fixtures (for tests) — test/fixtures/fix1/<feature>.js
- Export an array of records mirroring the table columns.
- Comment every record explaining its role and intentional relationships (e.g. "order2 belongs to user1 — used for ownership/access tests").
- Fixtures are BASELINES, not scenarios. Provide a clean, minimal, representative starting state. Do NOT make a fixture per test case (
fix1_product_inactive❌). Tests load the baseline and mutate it in-test (models.x.update(...)) for the scenario. - Only create a new set (
fix2) when the baseline topology is fundamentally different — not for a status/flag variation. - Respect FK ordering: parents before children.
database/sequence.js(auto-maintained byyarn gen) defines the load order, sopopulate()inserts in dependency order.
Compile the SQL fixture — yarn sql fix1
populate('fix1') in tests loads test/fixtures/fix1.sql, which is generated from the JS fixtures by yarn sql fix1 (it's gitignored and regenerated; yarn test runs it first). After editing any fix1/*.js, run yarn sql fix1 so the SQL reflects your changes.
Seed data (for dev) — database/seed/set1/<feature>.js
- Same idea for the development DB. Keep just a few "sets" with the bare minimum (don't proliferate sets — each must be updated on every schema change).
- Load with the seed command;
database/sequence.jscontrols order here too.
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.
- 7d ago First seen · 33 lines · 54 tokens per session scan A 391509eeeb10
add-fixtures is a skill published in the GitHub repository Hackbyrd/orbital-express (14 stars, last pushed 18d ago), licensed MIT. It adds 54 tokens to every session and 693 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
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…
volcengine-rds-postgresql
A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.