A command that copies database metadata, schemas, and table structures into an Oxy project. Metadata is information describing the database's tables and fields.

Use it to sync one selected database or all configured databases with Oxy.

It keeps the project's view of configured databases up to date, so later Oxy work can use the current structure. It also reports missing setup, warnings, and errors.

oxy:sync — Command by oxy-hq

Install

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.

agentmods

npx agentmods add commands/oxy-hq/skills/sync

Clone the repo

git clone --depth 1 https://github.com/oxy-hq/skills

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 573 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00573
Opus 5	$0.00006	$0.00287
Sonnet 5	$0.00002	$0.00115
Haiku 4.5	$0.00001	$0.00057

Measured 2d ago against content hash e414ae14b609, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

oxy:sync 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.

commands/sync.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sync Database Metadata

Extract and synchronize metadata, schemas, and table structures from your configured databases.

Pre-Sync Steps

Check for Oxy installation
- Run oxy --version to verify Oxy CLI is installed
- If not found, inform the user they need to install Oxy first
Read configuration
- Read config.yml to find configured databases
- Extract the list of database names under the databases: section
- If no databases configured, inform user and stop

Database Selection

Interactive selection
- Use AskUserQuestion to ask which database(s) to sync
- Options:
  - Each configured database as individual option
  - "All databases" option
- Allow single selection (recommend one database at a time for clarity)
Handle selection
- If user selects specific database: oxy sync <database-name>
- If user selects "All databases": oxy sync (without database argument)

Sync Process

Execute sync command
- Run the appropriate oxy sync command based on selection
- Show progress output to user
Monitor completion
- Wait for sync to complete
- Capture any errors or warnings

Success Actions

When sync completes successfully:

Report results

✅ Database sync completed!

Synced: <database-name>
Schema files saved to: .databases/<database-name>/

Tables synchronized: X

Show next steps
- Suggest: "Schema files are now available in .databases/ directory"
- Suggest: "You can now create semantic layer views based on these schemas"
- Suggest: "Run /oxy:build to compile your semantic layer"

Error Handling

If sync fails:

Show the full error message
Common issues and solutions:
- Connection failed: Check database credentials in config.yml
- Database not found: Verify database name in config.yml
- Authentication failed: Check API keys or credentials in environment variables
- Network error: Verify database host is accessible

Read the full file on GitHub · 86 lines

Changes

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 · 86 lines · 12 tokens per session scan A e414ae14b609

Subscribe to this mod's changes

oxy:sync 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 573 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.

Databases

oxy:sync

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Sync Database Metadata

Pre-Sync Steps

Database Selection

Sync Process

Success Actions

Error Handling

What this file has done since we first saw it

Other commands, from other repositories

git

checklist

clarify

specify

analyze

constitution