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 commands/oxy-hq/skills/buildgit 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/commands/oxy-hq/skills/build)<a href="https://agentmods.dev/commands/oxy-hq/skills/build"><img src="https://agentmods.dev/badge/commands/oxy-hq/skills/build.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.00012 | $0.00520 |
| Opus 5 | $0.00006 | $0.00260 |
| Sonnet 5 | $0.00002 | $0.00104 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
oxy:build 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 4d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Oxy Semantic Layer
Compile the semantic layer definitions into Cube.js schema and build vector embeddings for semantic search.
Pre-Build Steps
-
Check for Oxy installation
- Run
oxy --versionto verify Oxy CLI is installed - If not found, inform the user they need to install Oxy first
- Run
-
Check for semantic layer files
- Verify that
semantics/views/andsemantics/topics/directories exist and have files - If missing, inform the user they need to create view and topic files first
- Note:
oxy validatedoes NOT validate semantic layer files —oxy buildis the correct command for this
- Verify that
Build Process
-
Execute build command
- Run
oxy build - This compiles semantic layer definitions to Cube.js schema
- Builds vector embeddings for semantic search
- Run
-
Monitor output
- Show build progress to the user
- Report any errors or warnings that occur during build
Success Actions
When build completes successfully:
-
Report success with summary:
✅ Oxy build completed successfully! - Semantic layer compiled to Cube.js schema - Vector embeddings created Next steps: - Run `oxy semantic-engine --dev-mode` to test queries - Or use the semantic layer in your agents/workflows -
Offer next step
- Ask user if they want to start the semantic engine for testing
- If yes, inform them to run
oxy semantic-engine --dev-modein their terminal
Error Handling
If build fails:
- Show the full error message
- Identify which semantic layer file caused the error (if applicable)
- Suggest common fixes:
- Check entity key references match dimension names
- Verify all view names referenced in topics exist
- Ensure SQL expressions in dimensions/measures are valid
- Run
oxy syncif database schema has changed
Notes
- Build should be run after defining or modifying semantic layer files
- Requires a
semantics/directory with view and topic files - Database connections must be configured in config.yml
- Run
oxy syncfirst if working with database schemas
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.
- 4d ago First seen · 76 lines · 12 tokens per session scan A d3d1b8ff0fcc
oxy:build is a command published in the GitHub repository oxy-hq/skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 520 once invoked, about $0.0001 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 commands, from other repositories
querying
Query documents from a search index using type-safe filters with support for pagination, sorting, field selection, scoring, and highlighting. Count matching documents efficiently without returning results.
agent-brain-index
Index documents for semantic search.
agent
Add an AI agent / RAG backend (@convex-dev/agent) to the Convex app.
rag-publish-todo-list
Command "rag-publish-todo-list" from lucky-aeon/AgentX, covering rag 发布功能 todo list, 阶段一:数据库设计和基础架构 🗄️ ✅ 已完成, 1. 数据库表创建, 2. 领域层实现 and 3. 基础领域服务.
ingest
Manually add knowledge to the Weaviate store.
web-add
Ingest a single URL into the knowledge base.