Borrowing it
Nothing to install: this file belongs to oxy-hq/oxygen. 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/oxy-hq/oxygen/main/.claude/skills/oxy-compile-boundary/SKILL.mdgit 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-compile-boundary)<a href="https://agentmods.dev/skills/oxy-hq/oxygen/oxy-compile-boundary"><img src="https://agentmods.dev/badge/skills/oxy-hq/oxygen/oxy-compile-boundary/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-compile-boundary"><img src="https://agentmods.dev/badge/skills/oxy-hq/oxygen/oxy-compile-boundary.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.00157 | $0.02309 |
| Opus 5.5 | $0.00063 | $0.00924 |
| Sonnet 5.5 | $0.00031 | $0.00462 |
| Haiku 4.5 | $0.00016 | $0.00231 |
Grade A, and why
oxy-compile-boundary 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compile every workspace artifact to Postgres
Oxy's runtime no longer walks the workspace filesystem on customer-facing requests. PR #2460 (the compile boundary work) made every YAML entity addressable as a *_definitions row keyed by revision_id. A compile promotes a revision and every read site serves from Postgres until the next compile. The boundary is always on — there are no feature flags; a reader falls through to the filesystem only on a node that owns the files.
Where this is going (decided 2026-10-05): the server-side working copy is being removed. Compile becomes its own service that fetches a pushed commit; the filesystem fall-through disappears; the IDE goes. So "it is only read in the IDE" is no longer a reason to skip the boundary — a file the runtime needs and that is not compiled will have nowhere to be read from. Plan: internal-docs/factory-retirement.md.
This skill is the rule for anyone adding a new file type the runtime needs to read.
The contract: when you add a new .foo.yml
You owe all five of these before the feature ships. Skipping any one of them means the new file walks FS on every customer request — exactly what we just stopped doing.
-
Walker — add a
FileKind::Foovariant incrates/oxy-compile/src/walker.rsand a glob indiscover()so a compile pass finds the file. Root-only files go into the explicitif path.is_file()block (seeConfigandMonitorConfigas templates). Glob patterns go throughpush_glob.Your kind inherits two skip rules, and the working-copy lister must inherit the same two or the file resolves in the IDE and 404s on serve: any path COMPONENT that is dot-prefixed or
target/node_modules/dist/buildprunes at any depth (is_skipped), and any FILE NAME containing.test.drops as a fixture. The working-copy half of the second rule islist_entity_filesincrates/core/src/config/storage.rs— a newlist_foosgoes through it, not throughlist_by_sub_extensiondirectly. Both rules and why the walker wins ties:internal-docs/compile-boundary.md§ "What a workspace enumerates".
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 · 70 lines · 157 tokens per session scan A 732ae17774cf
oxy-compile-boundary is a skill published in the GitHub repository oxy-hq/oxygen (203 stars, last pushed yesterday), licensed Apache-2.0. It adds 157 tokens to every session and 2,309 once invoked, about $0.0006 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
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
convex-explain-app
Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.
platform-custom-field-generate
Use when users create, generate, or validate Salesforce Custom Field metadata. Trigger on custom fields, field types, Roll-Up Summary, Master-Detail/Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from a field, or scoping picklist values per record type; also…
field-service-sobject-create-configure
Headless 360 REST API deployment step for creating sObject records. Handles describe-based field discovery, required-field derivation, entity-relationship ordering, and composite graph transactions. Use this skill when a designer skill (or a user directly) needs to create sObject records after design confirmation…
durable-objects
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.
nornicdb-grpc
Drive NornicDB over gRPC — the Qdrant-compatible surface (Collections, Points, Snapshots) plus the additive NornicSearch service. Use when ingesting via Qdrant SDKs, migrating from Qdrant, or running hybrid text+vector search from a non-Bolt client. Covers connection, RPC catalog, collection→database mapping…