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 skills add oxy-hq/oxygen --skill oxy-data-architecturegit clone --depth 1 https://github.com/oxy-hq/oxygenWrote 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/oxy-hq/oxygen/oxy-data-architecture)<a href="https://agentmods.dev/skills/oxy-hq/oxygen/oxy-data-architecture"><img src="https://agentmods.dev/badge/skills/oxy-hq/oxygen/oxy-data-architecture/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/oxy-hq/oxygen/oxy-data-architecture"><img src="https://agentmods.dev/badge/skills/oxy-hq/oxygen/oxy-data-architecture.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.00127 | $0.02954 |
| Opus 5.5 | $0.00051 | $0.01182 |
| Sonnet 5.5 | $0.00025 | $0.00591 |
| Haiku 4.5 | $0.00013 | $0.00295 |
Grade A, and why
oxy-data-architecture 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 yesterday.
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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Oxy data architecture: where results get materialised
An OLAP store wants materialised results, not aggregation at query time. A dashboard that groups four million order rows on every page load is not a slow query to tune — it is a rollup that was never built. So the work that produces those tables has to be systematic: one place it runs, one guarantee about when it may read, one rule for what gets kept.
That spans Airway ingest, the semantic model, and scheduled automations, which is
why it is its own skill rather than a section in one of them — and it does not
restate them. Fold mechanics, duplicate rows and the pipeline lease are
oxy-airway-pipelines; views, measures and pre_aggregations syntax are
oxy-semantic-modeling; task syntax and schedules are oxy-automations.
The frame: bronze → silver → gold, as a lens
The medallion words are a useful way to think about how raw source data becomes analytics-ready. But nothing in Oxy — code, UI, schema names — says bronze, silver, gold, or medallion. Search a workspace for those words and you will not find a tier. An agent that searches, finds nothing, and invents a tier structure has invented it. Map the words onto what actually exists:
| medallion word | what is actually there |
|---|---|
| (transient) bronze buffer | <schema>_raw.<table> append buffer — replacing disposition only, not a tier |
| silver | <schema>.<table>, the normalized table a pipeline lands — every disposition ends here |
| gold | execute_sql rollup tables (*_daily_metrics) built by an automation, in the same schema |
| the promotion | the fold: watermark-bounded, latest-wins, merge-on-read — inline at the end of a load and again on the scheduled vacuum, identical SQL |
| storage | Airhouse = DuckLake on DuckDB (Parquet on object storage + a catalog) — for pipelines that land in Airhouse |
That last row is a default, not a law. A rollup lands wherever its execute_sql
step's database: points, so gold is not necessarily DuckLake: a gold table can
sit in a customer's ClickHouse with a semantic view (datasource: clickhouse)
modelled on top of it. That view is where the skills meet — a view models a
rollup an automation built — and it is the reminder to read the
database:/datasource: rather than assume the warehouse.
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.
- yesterday Changed · -15 lines · +127 tokens per session b8ed614710fc
- 2d ago First seen · 226 lines · 0 tokens per session scan A 7f950711d747
oxy-data-architecture is a skill published in the GitHub repository oxy-hq/oxygen (203 stars, last pushed yesterday), licensed Apache-2.0. It adds 127 tokens to every session and 2,954 once invoked, about $0.0005 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-10-14.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
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.
atlas-mssql
SQL Server specifics for Atlas (also Azure SQL and MSSQL): login, dev database and URL scope (mode=schema vs mode=database, the database query parameter), compatibility level and collation, system-generated constraint names, clustered index defaults and datetime2 precision in HCL, GO batches and the delimiter…
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…
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…