К основному содержанию
плагин CX Codex

dex — плагин для Claude Code: что делает и как установить

Плагин dex для аналитической инженерии: исследует хранилища данных, правит модели dbt и находит дрейф схем.

Apache-2.0 ★ 1 596 обновлён 2026-10-29

Установить в Claude Code · Через маркетплейс плагинов Все способы и платформы ↓
/plugin marketplace add hashgraph-online/awesome-codex-plugins
/plugin install dex@awesome-codex-plugins
Открыть на GitHub

Что делает dex

Dex встраивает в Claude Code и Codex сценарии работы дата-инженера через команды /dex:explore, /dex:transform и /dex:maintain. Плагин составляет карту таблиц хранилища, проверяет реальные связи между ключами, строит профили колонок и блокирует передачу персональных данных в контекст модели.

Преобразования данных и тесты dbt готовятся в виде диффов и запускаются только на dev-таргете. Исходные таблицы остаются нетронутыми, а перед платными запросами на облачных хранилищах движок выводит предварительную оценку стоимости.

Для запуска обязателен пакетный менеджер uv версии 0.13.4 или новее в переменной PATH: агент не установит его сам. Плагин работает только в среде с локальным шеллом и файлом .dex/config.yml, поэтому в веб-чате claude.ai запустить его не выйдет.

Какие задачи решает

  • Исследовать незнакомое хранилище данных и проверить внешние ключи
  • Сгенерировать модели dbt и метрики на изолированном dev-таргете
  • Найти дрейф колонок, объёма данных и определений метрик
  • Заблокировать попадание конфиденциальных данных в контекст LLM

Примеры запросов агенту

  • /dex:explore map
  • /dex:explore relationships --verify
  • /dex:maintain проверь дрейф схемы в dbt

Как установить dex

Через маркетплейс плагинов

/plugin marketplace add hashgraph-online/awesome-codex-plugins
/plugin install dex@awesome-codex-plugins

По шагам, с командами для каждой платформы: Плагины Claude Code: маркетплейсы, установка и как собрать свой

Вопросы о dex

Как установить dex в Claude Code?

Выполните по очереди две команды внутри Claude Code: /plugin marketplace add hashgraph-online/awesome-codex-plugins, затем /plugin install dex@awesome-codex-plugins.

Что делает плагин dex?

Он автоматизирует аналитическую инженерию: профилирует таблицы DWH, генерирует код для dbt и отслеживает расхождения в схемах данных.

Какие требования к окружению нужны для работы?

В системе должен быть установлен uv версии не ниже 0.13.4. Требуется доступ к локальному терминалу, поэтому плагин не работает в веб-интерфейсе claude.ai.

Исходный текст

dex · Apache-2.0
<picture>
  <source media="(prefers-color-scheme: dark)" srcset="assets/preview-dark.png" />
  <img alt="Dex: analytics engineering for your coding agent. Explore, transform, maintain." src="assets/preview-light.png" />
</picture>

# Dex

**Analytics engineering for your coding agent, with guardrails and lifecycle built into the engine.**

Dex lets your agent build your analytics: data warehouse exploration, dbt data transformation and semantic modeling, 
and schema-drift maintenance.

**Built by [Exmergo](https://www.exmergo.com)**

[![PyPI](https://img.shields.io/pypi/v/exmergo-dex-core?logo=pypi&logoColor=white&color=165dfc)](https://pypi.org/project/exmergo-dex-core/)
[![License](https://img.shields.io/badge/license-Apache--2.0-165dfc)](LICENSE)
[![data-eng-bench](https://img.shields.io/badge/data--eng--bench-57%25-33cf56)](benchmarks/data-eng-bench/README.md)
[![ADE-bench](https://img.shields.io/badge/ADE--bench-76%25-33cf56)](benchmarks/ade_bench/README.md)
[![CI](https://github.com/exmergo/dex/actions/workflows/ci.yml/badge.svg)](https://github.com/exmergo/dex/actions/workflows/ci.yml)

[![Docs](https://img.shields.io/badge/docs-docs.exmergo.com%2Fdex-165dfc?logo=readthedocs&logoColor=white)](https://docs.exmergo.com/dex)
[![LinkedIn](https://img.shields.io/badge/LinkedIn-Exmergo-165dfc?logo=linkedin&logoColor=white)](https://www.linkedin.com/company/exmergo/)
[![X](https://img.shields.io/badge/Follow-%40exmergo-165dfc?logo=x&logoColor=white)](https://x.com/exmergo)
[![Star the repo!](https://img.shields.io/github/stars/exmergo/dex?style=flat&label=Star%20the%20repo!%20%E2%AD%90&labelColor=555&logo=github&logoColor=white&color=165dfc)](https://github.com/exmergo/dex)

## Install

**Any agent** (run in your terminal):

```bash
npx skills add exmergo/dex
```

**Claude Code** (run these inside Claude Code, one at a time):

```
/plugin marketplace add exmergo/exmergo-agent-plugins
```

```
/plugin install dex@exmergo
```

**Codex**:

```bash
npx skills add exmergo/dex --agent codex
```

> [!IMPORTANT]
> **Dex needs [`uv`](https://docs.astral.sh/uv/) on your `PATH`.** No agent installs
> it for you. Run `brew install uv` or `pipx install uv`, or see the
> [uv installation docs](https://docs.astral.sh/uv/getting-started/installation/)
> for other platforms. `uv` supplies Python and the engine. Use uv 0.13.4 or
> later (`uv self update`): earlier releases still trust the emSign CA roots
> withdrawn after their keys were compromised.

In Claude Code the skills appear as `/dex:explore`, `/dex:transform`, and
`/dex:maintain` and trigger on matching intent. Update later with
`/plugin marketplace update exmergo`. Codex also gets a native plugin, with no MCP
server needed. Any other agent can be pointed at [`AGENTS.md`](AGENTS.md).

Run Dex from your project directory, so it finds your `.dex/config.yml` and keeps
its cache next to your project. Dex needs an agent with a local shell, so it does
not run in claude.ai chat.

> [!TIP]
> **Skip the first-run wait.** The first command installs the engine, which takes
> tens of seconds on a cold `uv` cache. Ask your agent to warm Dex once after
> installing, or run the command below in a CI or container build step. Add
> `--connector snowflake` (or any connector) to warm one before a project exists.

```bash
uv run --no-project --script skills/<skill>/scripts/run.py --warm
```

What you get:

- **Explore** a warehouse you have never seen. Ranked inventory, column profiles built from aggregates, PII flags, verified joins, and an ER diagram.
- **Transform** your dbt project and semantic layer. Models, tests, docs, and metrics arrive as reviewable plans and build only on a dev target.
- **Maintain** it as the world changes. Schema, volume, grain, and metric-definition drift, each with a proposed fix.

Your source data is never written to, and builds run on a dev target only. Cost
quoted before any spend. Every change is a diff you review. Works in Claude Code, Codex, or any agent that loads Agent Skills.

## Why

> *Most deadly errors arise from obsolete assumptions.*
>
> Frank Herbert, *Children of Dune*

A general coding agent is a good SQL author and a poor analytics engineer. It:

- re-learns the schema every session,
- has no strategy for a warehouse with thousands of tables,
- is blind to what a query costs,
- will happily pull personal data into its context,
- does not treat a dbt project or a semantic layer as an object to keep coherent over time.

Dex owns exactly that loop, and enforces its rules in the engine rather than in a prompt.

## Try it in three commands

No warehouse, no credentials, no cloud account, no network.

```bash
pip install "exmergo-dex-core[duckdb]"
dex demo
dex explore map
```

`dex demo` writes a small e-commerce DuckDB warehouse (`dex_demo.duckdb`, 7 tables,
29,512 rows) and a `.dex/config.yml` into the current directory, so every command
after it runs with no flags. It refuses rather than overwrite anything. The data
comes from a pinned seed, so what you see is what is written here.

`explore map` maps all 7 tables, infers 5 joins, flags 6 columns as personal data,
and reports 6 data-quality findings. Every command answers with one JSON envelope.
An excerpt, for one table:

```json
{
  "identifier": "dex_demo.main.order_items",
  "row_count": 14000,
  "grain": null,
  "data_quality": [
    "order_item_id is not unique: 13000 distinct over 14000 rows (1000 rows would have to be removed for it to be unique, so it is unique for 92.9% of rows); joins on it will fan out"
  ]
}
```

### It is broken on purpose

A first run that reports a clean bill of health teaches you nothing, so the demo
ships with real defects. Dig into them:

```bash
dex explore profile order_items products
dex explore relationships --verify
dex explore query "select email from customers"
```

- **A broken grain.** A batch was loaded twice, so `order_item_id` is unique for only 92.9% of rows. Dex reports the duplicates and leaves the grain unknown rather than guessing a key.
- **A key that mixes id schemes.** `sku` is `90% numeric, 10% 32-character hexadecimal (md5-shaped)`. Cast it to a number and you silently drop 10% of products.
- **A join that looks right and is not.** `web_events.customer_id` shares a name with the CRM's key, but verification finds 100% of its values have no match.
- **A refusal.** The query firewall will not put `customers.email` into context. `select count(distinct email) from customers` runs, because a statistic is not a value.

There is also a table an interrupted load left empty, two columns whose declared
type contradicts their content, and two designed PII false positives. See the
[`dex demo` reference](https://docs.exmergo.com/dex/cli/demo).

> [!NOTE]
> DuckDB is free and local, so nothing here asks you to confirm a spend. On a
> metered warehouse the same commands return an estimate first and run only once
> you agree to it.

## How it works

```mermaid
flowchart LR
  Agent[Coding agent] --> Skills[Dex skills]
  Skills --> Engine[exmergo-dex-core engine]
  Engine -->|SELECT-only SQL, cost-capped| Warehouse[(Your warehouse)]
  Engine -->|dbt builds, dev target only| Warehouse
  Engine -->|one sanitized JSON envelope| Agent
  Engine -->|plans as diffs| Repo[Your repository: dbt project + semantic layer]
  Engine <--> Cache[.dex/ cache and snapshot]
```

The skills are thin. All the logic, and every guardrail, lives in one engine
(`exmergo-dex-core`) behind a [small command contract](https://docs.exmergo.com/dex/reference/command-contract).
Your repository is the source of truth on two independent axes: the transformation
project (dbt) and the semantic layer. The `.dex/` directory is only a cache.

### Explore

Rank what matters, profile selectively, infer and verify joins, answer ad-hoc
questions through a PII-aware query firewall, read and query the semantic layer,
and draw the map as a Mermaid ER diagram. Fully read-only.
[Skill](skills/explore/SKILL.md) · [methodology](https://docs.exmergo.com/dex/concepts/methodology) · [commands](https://docs.exmergo.com/dex/cli/explore)

<img width="522" height="343" alt="Explore" src="https://github.com/user-attachments/assets/7f16b370-66ed-4596-ae01-041cf3db3525" />

### Transform

Author and refactor dbt models from staging to marts, with tests and docs, plus the
semantic layer on top. Every change is a stored plan you review, then apply. Builds
run against a dev target only.
[Skill](skills/transform/SKILL.md) · [what Dex writes](https://docs.exmergo.com/dex/concepts/dbt-project) · [commands](https://docs.exmergo.com/dex/cli/transform)

<img width="504" height="271" alt="Transform" src="https://github.com/user-attachments/assets/fda40e48-b481-424c-adc7-d79c0ede346b" />

### Maintain

Diff the warehouse, the project, and the semantic layer against the last snapshot,
rank the drift by blast radius, and propose the reconciling edits. `maintain verify`
checks a project as it stands, with no baseline needed.
[Skill](skills/maintain/SKILL.md) · [commands](https://docs.exmergo.com/dex/cli/maintain)

<img width="484" height="344" alt="Maintain" src="https://github.com/user-attachments/assets/ff714eaf-f0b2-46d6-8a4b-c69791740f18" />

### What to commit in `.dex/`

Dex keeps its working state in `.dex/`. Most of it is safe to commit; the
exception is any file that can carry data values. Commit the lockfile and the
config, and keep the exploration cache out of a repo that must not publish
data values:

| File | Commit? | Can it contain data values? |
| --- | --- | --- |
| `.dex/config.yml` | Yes | No: connector targets, `pii_overrides` (column names, not values), budgets and limits. Credentials live in environment variables or dbt profiles, never in this file. |
| `.dex/snapshot.json` | Yes, like a lockfile | Yes: when snapshotted from a cache it pins the cache's datasets wholesale, including each non-PII column's capped value domain and min/max. A metadata-only baseline (no cache) carries schema and volume only. PII-flagged columns never carry value domains. |
| `.dex/cache.json` | Only if values may be public | Yes: column profiles with capped value domains (actual values with counts). Never for PII-flagged columns. |
| `.dex/plans/*.json` | Optional, as an audit trail | No warehouse values: the proposed contents of project files. |
| `.dex/queries.jsonl` | Optional, as a ledger | SQL text, which may hold literals. |
| `.dex/drift.json` | No: regenerate with `maintain check` | Aggregates only: counts, names and schema metadata in drift findings. |

For a repo that must not publish data values, ignore the rest:

```gitignore
# Dex state that can publish data values, or is local-only output.
.dex/cache.json
.dex/dex.db
.dex/dex.db-journal
.dex/queries.jsonl
.dex/drift.json
.dex/spend.jsonl
.dex/spend.lock
```

`.dex/dex.db` is the SQLite backend's equivalent of `cache.json`, so it gets
the same caution. `.dex/spend.jsonl` is the billed-command ledger: byte
counts, job ids and statement hashes only, never SQL values or credentials,
but it is local spend history, so there is no reason to commit it.

### What Dex will never do

- **Write to your source data.** Dex's own SQL is SELECT-only. The only writes to your warehouse are the dbt builds you confirm, on a dev target.
- **Put personal data in your agent's context.** PII is flagged by column, category, and confidence, and never surfaced. Only a human clears a flag. ([PII policy](https://docs.exmergo.com/dex/guardrails/pii-policy))
- **Spend before quoting.** A metered scan returns an estimate and runs only with your confirmation and a budget. ([cost controls](https://docs.exmergo.com/dex/guardrails/cost-controls))
- **Change your project behind your back.** Every edit is a diff, and a human edit made since planning is never overwritten. ([source of truth](https://docs.exmergo.com/dex/concepts/source-of-truth))
- **Build anywhere but dev.** Prod-looking targets are refused outright.

## Connectors

| Connector | Type | Self-hostable | Extra / `--connector` | Cost surfaced as | Credentials from |
| --- | --- | :---: | --- | --- | --- |
| <img src="https://www.exmergo.com/connectors/snowflake.png" width="20" height="20" alt=""> [**Snowflake**](https://docs.exmergo.com/dex/connectors/snowflake) | Cloud warehouse | ❌ | `snowflake` | Warehouse-seconds, with credits | `connections.toml`, `SNOWFLAKE_*` env, or a dbt profile |
| <img src="https://www.exmergo.com/connectors/bigquery.png" width="20" height="20" alt=""> [**BigQuery**](https://docs.exmergo.com/dex/connectors/bigquery) | Cloud warehouse | ❌ | `bigquery` | Bytes scanned | Application Default Credentials |
| <img src="https://www.exmergo.com/connectors/databricks.png" width="20" height="20" alt=""> [**Databricks**](https://docs.exmergo.com/dex/connectors/databricks) | Cloud warehouse | ❌ | `databricks` | Warehouse-seconds, with DBUs | `databricks auth login`, `DATABRICKS_*` env, or a dbt profile |
| <img src="https://www.exmergo.com/connectors/redshift.png" width="20" height="20" alt=""> [**Amazon Redshift**](https://docs.exmergo.com/dex/connectors/redshift) | Cloud warehouse, Serverless-first | ❌ | `redshift` | Compute-seconds, with RPU-hours | The AWS credential chain or `REDSHIFT_*` env |
| <img src="https://www.exmergo.com/connectors/clickhouse.png" width="20" height="20" alt=""> [**ClickHouse**](https://docs.exmergo.com/dex/connectors/clickhouse) | Analytical database | ✅ | `clickhouse` | Compute-seconds on Cloud, database-seconds self-hosted | `CLICKHOUSE_URL`, `CLICKHOUSE_*` env, or a dbt profile |
| <img src="https://www.exmergo.com/connectors/trino.png" width="20" height="20" alt=""> [**Trino**](https://docs.exmergo.com/dex/connectors/trino) | Federated query engine (Trino, Starburst Enterprise, Trino on EMR) | ✅ | `trino` | Cluster-seconds | `TRINO_URL`, `TRINO_*` env, or a dbt profile |
| <img src="https://www.exmergo.com/connectors/duckdb.png" width="20" height="20" alt=""> [**DuckDB**](https://docs.exmergo.com/dex/connectors/duckdb) | Embedded analytical | ✅ | `duckdb` | Free and local | None, just a file path |
| <img src="https://www.exmergo.com/connectors/postgresql.png" width="20" height="20" alt=""> [**Postgres**](https://docs.exmergo.com/dex/connectors/postgres) | Operational database | ✅ | `postgres` | Database-seconds | `pg_service.conf`, `DATABASE_URL`, `PG*` env, or a dbt profile |

Credentials are discovered, never asked for, and never enter the agent's context.
Every scan is estimated, confirmed, and capped server-side, and settled spend is
recorded in a local ledger ([cost controls](https://docs.exmergo.com/dex/guardrails/cost-controls)).
Self-hosted databases bill no dollars and are still gated, because an unbounded
scan on a production Postgres primary is a real cost too.

**Coming next:** MotherDuck, Starburst Galaxy, Microsoft Fabric.

## Semantic layers

The semantic layer is its own axis, chosen once per repository in `.dex/config.yml`.
With Ossie or SLayer, it needs no dbt project at all. ([overview](https://docs.exmergo.com/dex/semantic-layers/overview))

| Semantic layer | Hosted | Queryable | `vendor` / `deployment` | Read through |
| --- | :---: | :---: | --- | --- |
| <img src="https://www.exmergo.com/connectors/dbt.png" width="20" height="20" alt=""> **dbt** | ✅ | ✅ | `dbt` / `local` or `dbt_cloud` | MetricFlow locally, run through the Dex connector and its cost guard, or the hosted dbt Cloud Semantic Layer API |
| <img src="https://www.exmergo.com/connectors/ossie.png" width="20" height="20" alt=""> **[Apache Ossie](https://github.com/apache/ossie)** (incubating) | ❌ | ❌ | `ossie` / `local` | Native documents in the repository, no dbt or MetricFlow in the path |
| **[SLayer](https://github.com/MotleyAI/slayer)** | ❌ | ✅ | `slayer` / `local` | SLayer model files, validated by one pinned release; SLayer renders, Dex runs it under the cost guard |

Ossie is catalog-first because the format specifies interchange metadata and no
query runtime, so Dex reads, authors, and checks an Ossie layer but refuses a metric
query by name rather than inventing semantics. See the
[Ossie page](https://docs.exmergo.com/dex/semantic-layers/ossie) and the
[Ossie tutorial](https://docs.exmergo.com/dex/guides/ossie-semantic-layer).

**Coming next:** Cube, Snowflake Semantic Views, Looker / LookML, and Databricks Metric Views.

## See it on a real project

**[github-repo-analytics](https://github.com/exmergo/github-repo-analytics)** is a template that tracks GitHub traffic, stars, downloads and contributors for your open-source projects, free on GitHub Actions.   
Every model and metric was built and is maintained with Dex. Its [audit trail](https://github.com/exmergo/github-repo-analytics/blob/main/.dex/review/README.md) holds the raw envelopes, including the drift Dex blocked.

## The Core Python Library you can use

The engine is a plain Python package, `exmergo-dex-core`:

```bash
pip install exmergo-dex-core     # or: uv add exmergo-dex-core
```

Drive the same loop from Python instead of parsing CLI output:

```python
from exmergo_dex_core import DexEngine

with DexEngine(connector="duckdb", path="shop.duckdb") as eng:
    mapped = eng.map()                  # a DexCache, not a JSON blob
    rows = eng.query("select status, count(*) from orders group by status")

print(mapped.relationship_count, rows.cells)
```

Every guarantee the CLI makes holds here, because it is the same code. An
unconfirmed billed call raises `ConfirmationRequiredError` carrying the estimate.
By default nothing is written to disk; `DexEngine.from_repo("path/to/repo")` opts in
to a project on disk, the way the CLI does.

For hosts embedding Dex:

- **Values-free mode** keeps every table value out of the model's view, aggregates only. ([values-free mode](https://docs.exmergo.com/dex/guardrails/values-free-mode))
- **Per-user credentials**: pass a `ConnectionSource` so each request reaches the warehouse as its own principal.
- **Multi-process lifecycles**: export a plan, verify and apply it elsewhere, and get typed evidence of what a build established. ([host integration](https://docs.exmergo.com/dex/reference/host-integration))
- **Other formats and stores**: plug in a [project format](https://docs.exmergo.com/dex/reference/project-formats) or a [storage backend](https://docs.exmergo.com/dex/reference/storage-backends).

More in the [package README](packages/dex-core/README.md).

## Benchmarks

We run Dex on two public analytics-engineering benchmarks and commit every run's
raw per-task results, including the ones that flatter us least.

| Benchmark | Setup | Result | Details |
|---|---|---|---|
| **data-eng-bench** (Snowflake, 103 tasks) | Dex + Claude Sonnet 5 | **57.3%** resolved, 89.7% of assertions pass | [README](benchmarks/data-eng-bench/README.md) |
| **ADE-bench** (dbt Labs, 75 tasks) | Dex + Claude Sonnet 5 | **76%** resolved, at 2.5x lower cost than Fable 5 | [README](benchmarks/ade_bench/README.md) |

<img width="719" height="283" alt="ADE-bench accuracy and cost by model" src="https://github.com/user-attachments/assets/9f8bca64-6508-4590-9fa7-bb1ac077263d" />

We believe that benchmarks are important, but not as important as user/agent experience.  
Trust in a diff, cost surfaced before spend, and sensitive data kept out of context. We optimize for that experience
and treat these scores as guide posts. ([evaluation](https://docs.exmergo.com/dex/reference/evaluation))

## What Dex sends where

- **On install**, `uv` downloads the pinned engine (and a Python 3.11 to 3.14 if you have none) from PyPI or your configured index.
- **Your warehouse** gets SELECT-only SQL from Dex, plus the dbt builds you confirm on a dev target, with credentials from your existing credential chain.
- **dbt Cloud** is contacted only if you enable the hosted semantic layer.
- **dbt-core**, when Dex runs it, sends dbt Labs its own anonymous usage statistics unless you turn them off. `transform deps` downloads the packages your `packages.yml` declares.
- **Your repository** holds Dex's state in `.dex/`. dbt writes its usual `target/` and `logs/`.

> [!IMPORTANT]
> **Dex sends nothing to Exmergo.** No telemetry, analytics, license check, or
> update ping. See the [Dex privacy policy](https://www.exmergo.com/privacy/dex).

## Further reading

- [Documentation](https://docs.exmergo.com/dex): start here
- [CLI reference](https://docs.exmergo.com/dex/cli/overview): every command and flag
- [Command contract](https://docs.exmergo.com/dex/reference/command-contract) and [`AGENTS.md`](AGENTS.md): how any agent drives the engine
- [Cost controls](https://docs.exmergo.com/dex/guardrails/cost-controls) and [PII policy](https://docs.exmergo.com/dex/guardrails/pii-policy): the two guardrails that cut across everything
- [Configuration](https://docs.exmergo.com/dex/cli/config): read and change `.dex/config.yml` as a confirmed diff
- [Connectors](https://docs.exmergo.com/dex/connectors/duckdb): setup, cost, and read-only enforcement per warehouse
- [Changelog](https://docs.exmergo.com/dex/changelog)
- [`references/`](references/): the same material as Markdown, for agents and offline reading

## Dex Enterprise

Dex Enterprise runs Dex as automated workflows in your own CI. It turns tickets into
draft pull requests with `explore` and `transform`, and runs `maintain` on a schedule
to turn drift into draft pull requests for your engineers to review. No Exmergo
service sits in the request path, and everything in this repository stays
Apache-2.0. [Learn more](https://www.exmergo.com/dex/enterprise).

## Community

### Community Integrations

**[dagster-dex](https://github.com/catincloud-labs/dagster-dex)**, maintained by
CatInCloud Labs, lets Dex read a Dagster asset graph instead of a dbt project, so
exploration and drift maintenance run natively against your orchestrated assets.

### Connect with the Community

Join the agent-native data/analytics community!

- 🌟 [Star Us on GitHub](https://github.com/exmergo/dex/)
- 👾 [Join Our Discord Community](https://www.exmergo.com/discord)
- 🔗 [Follow Us on LinkedIn](https://www.linkedin.com/company/exmergo/)
- 🐦 [Follow Us on X](https://x.com/exmergo)
- 🔨 [Follow Us on GitHub](https://github.com/exmergo/)

## Contributing

See [CONTRIBUTING.md](CONTRIBUTING.md) for local setup, linting, the pre-commit
hook, and changelog fragments. Every pull request into `main` must pass Lint and
CI, and adds a fragment under [`changelog.d/`](changelog.d/) unless no user can
see the change. Please also read the [code of conduct](CODE_OF_CONDUCT.md).

## License

Apache-2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).

© Exmergo, Inc. · Apache-2.0 · hashgraph-online/awesome-codex-plugins

Похожие плагины

Все плагины по теме «Данные и базы» →
altimate-data-engineering-skills reason-machines Скилл altimate-data-engineering-skills для Claude Code помогает аналитикам и инженерам данных проектировать модели dbt, находить ошибки сборки и оптимизировать медленные запросы Snowflake. CX Codex +1 2 100установок pipeverify akshaysharma1088 MCP-сервер pipeverify для Claude Code, который проверяет изменения в пайплайнах данных и возвращает статус PASS, REVIEW или BLOCK. CX Codex +1 ★ 5звёзд репо ktx-ai-data-agents reason-machines Скилл ktx-ai-data-agents учит ИИ-агентов использовать ktx: собирать семантический слой из dbt и баз данных, искать проверенные метрики и строить точные SQL-запросы. CX Codex +1 156установок using-dbt-state dbt-labs Скилл using-dbt-state для Claude Code, который объясняет агенту, как работает dbt State — серверный механизм переиспользования узлов. Помогает включать, настраивать и отлаживать пропуск или клонирование моделей вместо полной перестройки. CX Codex +1 591установок orionbelt-semantic-layer ralforion MCP-сервер orionbelt-semantic-layer, который компилирует YAML-модели в SQL для BigQuery, Snowflake, DuckDB и ещё пяти диалектов. Агент описывает метрики и измерения один раз, потом задаёт вопросы на человеческом языке. CX Codex +1 ★ 104звёзд репо dbt-sf-to-bq-translator официальный google Скилл dbt-sf-to-bq-translator для Claude Code, Gemini CLI и Codex транслирует SQL-модели dbt из Snowflake в BigQuery. Запускается при переносе существующего dbt-пайплайна с одной платформы на другую. CX Codex +1 2 300установок

Из того же набора391

Весь набор →
dropthehassle Плагин учит агента публиковать собранный сайт на бесплатный HTTPS-адрес yourname.dropthehassle.app или свой домен через DropTheHassle. CX Codex ★ 1 596звёзд репо droplinked-codex-plugin Плагин droplinked-codex-plugin подключает агента к удалённому MCP-серверу droplinked для поиска верифицированных товаров, проверки ончейн-аттестаций продавцов и оформления заказов прямо из диалога. CX Codex ★ 1 596звёзд репо dodopayments Плагин dodopayments для Claude Code и Codex подключает интеграцию Dodo Payments к задачам с платежами, подписками и биллингом. Агент загружает подходящий скилл по запросу и может обращаться к API и документации через MCP. CX Codex ★ 1 596звёзд репо digital-marketing-pro Плагин digital-marketing-pro для Claude Code и Codex проводит каждый бренд по маршруту из 12 частей и формирует четыре основных документа. Помогает вести много брендов. CX Codex ★ 1 596звёзд репо design-os-3d-blender Плагин design-os-3d-blender для Claude Code и Codex создаёт параметрические механические детали в Blender и проверяет их геометрию. Готовит модели к экспорту в 3D-форматы. CX Codex ★ 1 596звёзд репо deed-page Плагин deed-page публикует HTML-файлы и папки со статикой на постоянный публичный адрес без регистрации и API-ключей. CX Codex ★ 1 596звёзд репо dataproduct-builder-dbt Плагин dataproduct-builder-dbt для Claude Code и Codex ведёт dbt-проект от скаффолдинга до синхронизации метаданных с Entropy Data. Строит модели по требованиям из ODCS-файла. CX Codex ★ 1 596звёзд репо darkmoon MCP-сервер для вашего self-hosted Darkmoon Pro: запускает авторизованный пент-тест, показывает статус прогона, кампании и находки прямо из агента. CX Codex ★ 1 596звёзд репо

Спонсоры проекта

Компании, которые помогают держать аналитику открытой