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-coregit clone --depth 1 https://github.com/oxy-hq/skillsWhat 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.00989 | $0.00989 |
| Opus 5 | $0.00495 | $0.00495 |
| Sonnet 5 | $0.00198 | $0.00198 |
| Haiku 4.5 | $0.00099 | $0.00099 |
Grade A, and why
oxy-core 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Oxy Project Conventions
You are working in an Oxy data project. Oxy is a framework for building data apps with semantic layers, SQL workflows, AI agents, and interactive dashboards.
File Conventions
| Pattern | Purpose |
|---|---|
config.yml |
Project configuration (databases, settings) |
semantics.yml |
Semantic layer entry point |
*.view.yml |
Semantic layer views (entities, dimensions, measures) |
*.topic.yml |
Semantic layer topics (organize views by domain) |
*.workflow.yml |
Multi-step data pipelines |
*.agent.yml |
AI-powered analysis agents |
*.app.yml |
Data app dashboards (tasks + displays) |
.databases/ |
Auto-generated database schemas (from oxy sync) |
etl/ |
ETL pipelines using DLT |
The Oxy Hierarchy
When solving data analysis problems, follow this priority order:
Does the semantic layer have the data?
├─ YES -> Use semantic queries (PREFERRED)
└─ NO -> Is this a deterministic query/pipeline?
├─ YES -> Use SQL file or Workflow
└─ NO -> Need AI reasoning?
├─ YES -> Use an Agent
└─ NO -> Build semantic layer views first, then use semantic queries
- Semantic Queries (preferred): Use when views/topics exist covering the data. Natural language, automatic joins, centrally maintained.
- SQL / Workflows (fallback): Use when data isn't in semantic layer, or you need custom logic, ETL, or parameterized queries.
- AI Agents (last resort): Use only when you need AI reasoning, exploratory analysis, or dynamic query generation.
Always check if semantic layer views exist before writing SQL or agents.
CLI Commands Reference
| Command | Purpose |
|---|---|
oxy sync |
Extract database schemas to .databases/ |
oxy sync <db-name> |
Sync a specific database |
oxy validate |
Validate all YAML configs (agents, workflows, apps, semantic layer) |
oxy validate --file=<path> |
Validate a single file |
oxy build |
Compile semantic layer and build vector embeddings |
oxy run query.sql |
Execute a SQL file |
oxy run query.sql --dry-run |
Test SQL without executing |
oxy run query.sql -v key=value |
Run SQL with variables |
oxy run pipeline.workflow.yml |
Run a workflow |
oxy run agent.agent.yml "question" |
Run an agent with a prompt |
oxy test <file> |
Run evaluation tests on agent/workflow |
oxy semantic-engine --dev-mode |
Start semantic engine for testing queries |
oxy start |
Start the web UI for rendering apps |
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 · 96 lines · 989 tokens per session scan A b62a57791571
oxy-core is a cursor rule published in the GitHub repository oxy-hq/skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 989 tokens to every session, about $0.0049 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-31.
Other cursor rules, from other repositories
spring-ai-rag-demo-module
Spring AI RAG Demo 项目专属架构与编码约束.
ml-engineer
Designs, builds, and manages the end-to-end lifecycle of machine learning models in production. Specializes in creating scalable, reliable, and automated ML systems. Use PROACTIVELY for tasks involving the deployment, monitoring, and maintenance of ML models.
langfuse
Langfuse is an LLM observability tool used to monitor LLM behavior in our application. It uses decorators and callbacks to record LLM inference. Always use it in LLM-related modules to ensure traceability.
clarify-first-prompting
Clarify-first strategy: detect ambiguity, ask targeted questions, expand simple prompts into detailed specifications.
cursorrules
Cursor rule "cursorrules" from Clarity-Digital-Twin/brain-go-brrr, covering .cursorrules - brain-go-brrr project (fixed architecture), rule #1: no parallel implementations ever, experiments/trainanything.py - must be thin, rule #2: check before building and rule #3: normalization is critical.
standards-data-eng
Mandatory standards for Python and SQL data pipelines.