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 instructions/exmergo/dex/agents-mdgit clone --depth 1 https://github.com/exmergo/dexWhat 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.09733 | $0.09733 |
| Opus 5 | $0.04866 | $0.04866 |
| Sonnet 5 | $0.01947 | $0.01947 |
| Haiku 4.5 | $0.00973 | $0.00973 |
Grade C, and why
dex AGENTS.md scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
(`curl -LsSf https://astral.sh/uv/install.sh | sh`, or `brew install uv`, or Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
(`curl -LsSf https://astral.sh/uv/install.sh | sh`, or `brew install uv`, or How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dex: driving the engine from any agent
dex is the agent-native analytics engineering toolkit. All logic lives in one
portable engine, exmergo-dex-core; this file tells any coding agent how to drive
it. On Claude Code the three skills (explore, transform, maintain)
auto-trigger and do this for you. On other agents, follow the contract below
directly. The guardrails and outputs are identical because they live in the
engine, not here.
The loop: Explore, Transform, Maintain (ETM)
- Explore an unfamiliar warehouse or DuckDB database: rank what matters, profile selectively, infer joins, persist a draft map.
- Transform the dbt project: author and refactor dbt SQL models (staging to marts) with tests and docs, and author the semantic layer on top (entities, dimensions, measures, metrics) as dbt semantic models (MetricFlow YAML). Both are the same job, reviewable diffs to the dbt project.
- Maintain the project as the world changes: diff the current warehouse and
dbt against the last
.dex/snapshot, surface schema, volume, grain, and definition drift, and propose the reconciling edits.
The command contract
The engine exposes one small, stable command surface. Run a subcommand, read the
single JSON envelope it prints to stdout, decide the next step. State persists in
.dex/, so subcommands are stateless and you orchestrate multi-step flows.
uv run python -m exmergo_dex_core <subcommand> [flags]
# or, with the pinned wrapper a skill ships:
uv run scripts/run.py <subcommand> [flags]
Both forms need uv on PATH: it is what installs
and runs the engine, and no agent host installs it for you. Without it the shell
reports uv: command not found, and the shipped wrapper run directly refuses with
an error envelope (reason: prerequisite) naming the fix. The install is one line
(curl -LsSf https://astral.sh/uv/install.sh | sh, or brew install uv, or
pipx install uv); relay it to the user rather than reaching for another way to do
the work, since every guardrail below lives in the engine.
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 · 252 lines · 9,733 tokens per session scan C 55df74174c97
dex AGENTS.md is an instructions file published in the GitHub repository exmergo/dex (24 stars, last pushed 3d ago), licensed Apache-2.0. It adds 9,733 tokens to every session, about $0.0487 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
tuva-core AGENTS.md
Instructions for tuva-health/tuva-core, covering tuva core agent operating manual, tuva core 1.0 contract, repository boundaries, architecture and public-contract rules and extension columns.
strata-oss AGENTS.md
AGENTS.md instructions for G-Schumacher44/strata-oss, covering strata agent rules, collaboration model, the conductor loop, authority order and required reading (start here).
InvestSkill GEMINI.md
Instructions for yennanliu/InvestSkill, covering investskill — gemini cli setup & usage guide, installation & setup, quick start, navigate to the investskill directory and start gemini cli (loads gemini.md automatically).
she-love-me CLAUDE.md
Instructions for 863401402/she-love-me, covering claude.md and 唯一工作流.
wayland-core copilot-instructions.md
Instructions for FerroxLabs/wayland-core, covering ijfw rules, output discipline, memory routing, context discipline and cross-audit.
ZipAgent AGENTS.md
Instructions for JiayuXu0/ZipAgent, covering repository guidelines, project structure & module organization, build, test & development commands, coding style & naming conventions and testing guidelines.