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 rules/oxy-hq/skills/oxy-semantic-layergit clone --depth 1 https://github.com/oxy-hq/skillsWrote 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/rules/oxy-hq/skills/oxy-semantic-layer)<a href="https://agentmods.dev/rules/oxy-hq/skills/oxy-semantic-layer"><img src="https://agentmods.dev/badge/rules/oxy-hq/skills/oxy-semantic-layer.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 | $0.00000 | $0.04243 |
| Opus 5 | $0.00000 | $0.02122 |
| Sonnet 5 | $0.00000 | $0.00849 |
| Haiku 4.5 | $0.00000 | $0.00424 |
Grade A, and why
oxy-semantic-layer 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 3d 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 — 571 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Oxy Semantic Layer Builder
Build and maintain Oxy semantic layer files (views and topics) that enable business users to query data using natural language.
Core Workflow
- Analyze schemas: Read
semantics.yml(produced byoxy sync) to understand table structures. If a legacy.databases/directory exists, read that instead. - Create views: Build
semantics/views/*.view.ymlfiles with entities, dimensions, and measures - Create topics: Build
semantics/topics/*.topic.ymlfiles to organize views - Validate: Run
oxy buildto check syntax and compilation (do NOT useoxy validateon view/topic files) - Test: Use
oxy semantic-engine --dev-modeto verify queries work
View File Structure
Views are the core of the semantic layer. Each view file (semantics/views/*.view.yml) defines:
name: view_name
description: "Clear business explanation of what this view represents"
datasource: "database_name" # Must match config.yml
table: "schema_name.table_name"
entities:
- name: entity_name
type: primary|foreign
description: "What this entity represents"
key: dimension_name # MUST reference a dimension name, not a column
dimensions:
- name: dimension_name
type: string|number|date|datetime|boolean
description: "Business-friendly explanation"
expr: column_name_or_sql_expression
samples: ["example1", "example2"] # Optional but helpful
synonyms: ["alias1", "alias2"] # For natural language queries
measures:
- name: measure_name
type: sum|average|count|count_distinct|min|max|median|stddev|custom
description: "What this metric represents"
expr: column_name_or_sql_expression
synonyms: ["alternative name"]
filters: [] # Optional, for filtered measures
Entity Design (Critical for Joins)
Entities enable automatic joins between views. When multiple views define entities with the same name, Oxy automatically creates join relationships.
Entity Types
- Primary entity: The main subject of the view (one per view, required)
- Foreign entity: References to objects in other views (creates relationships)
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.
- 3d ago First seen · 571 lines · 0 tokens per session scan A b28eb60facee
oxy-semantic-layer is a cursor rule published in the GitHub repository oxy-hq/skills (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,243 tokens. 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-31.
Other cursor rules, from other repositories
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-backward-compatibility
Do not add backward-compatibility shims or migration scaffolding.
sqlmodel
Satisfying the type checker when working with SQLModel.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
database
Database rules — apply when working with database schemas, queries, migrations, or ORM models.