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 skills add exmergo/dex --skill exploregit clone --depth 1 https://github.com/exmergo/dexWrote 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/skills/exmergo/dex/explore)<a href="https://agentmods.dev/skills/exmergo/dex/explore"><img src="https://agentmods.dev/badge/skills/exmergo/dex/explore/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/exmergo/dex/explore"><img src="https://agentmods.dev/badge/skills/exmergo/dex/explore.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00232 | $0.03432 |
| Opus 5.5 | $0.00093 | $0.01373 |
| Sonnet 5.5 | $0.00046 | $0.00686 |
| Haiku 4.5 | $0.00023 | $0.00343 |
Grade A, and why
explore 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 yesterday.
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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explore
Make sense of a warehouse or a local DuckDB database the way an analytics
engineer does: rank what matters, drill selectively, and persist a draft map in
.dex/. This skill is read-only: it writes nothing but the .dex/ cache.
Procedure
dex works in one loop: explore, transform, maintain. Every step runs one engine command, reads the single JSON envelope it prints, and decides the next step from that envelope.
- Explore before you write. Before writing or fixing SQL against a table
whose columns, types, grain, or join keys you have not verified in this
session, run
explore map(orexplore profile <tables>for a few named ones) and read its grain, keys, PII flags, and data-quality findings. Answer ad-hoc questions withexplore query, never with a raw database client. - Plan the change. Author the file content and hand it to
transform plan(orsemantic define|update|planfor the semantic layer). Nothing is written yet. Read the diffs, thewarnings, and, on a model that already exists,data.row_attribution; re-plan until they describe the change you meant. - Apply it.
transform apply <plan-id>writes the plan as a reviewable git diff. A human edit made since planning comes back asneeds_confirmation: re-plan against the current files. - Build and verify on dev. Run
transform build --target dev --verify. Readdata.verification.ranfirst, then relay the findings and anything undersuppressed. A green build says dbt ran, not that the rows are right. - Maintain.
maintain checkcompares the warehouse and the project with the.dex/snapshot.jsonbaseline, andmaintain verifychecks the project as it is now with no baseline.maintain reconcileproposes the fix as a plan, applied withtransform apply. Takemaintain snapshotafter a known-good build.
At every step: a needs_confirmation envelope waits on the user's decision (a
spend, or a dex config diff), never on yours; only a human clears a PII
flag; and you never edit the dbt project, .dex/config.yml, .dex/cache.json,
or .dex/plans/ by hand in place of the command that guards them.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · +7 lines · +4 tokens per session fc94ef5a8f16
- 2d ago Changed · +10 lines 9196a6449587
- 6d ago Changed · +8 lines · -117 tokens per session 3f4666894548
- 8d ago Changed · +10 lines 3370e80c33dd
- 9d ago Changed · +1 lines scan C → A ffe5f82dc317
- 12d ago Changed · -200 lines 44069bc62a02
- 1mo ago Changed · +6 lines 99d1ca5d2b5b
- 1mo ago Changed · +12 lines · +36 tokens per session 168180eb6a53
- 1mo ago Changed · +31 lines 3b76cb316ae2
- 1mo ago First seen · 335 lines · 309 tokens per session scan C a8ea3967da88
explore is a skill published in the GitHub repository exmergo/dex (88 stars, last pushed today), licensed Apache-2.0. It adds 232 tokens to every session and 3,432 once invoked, about $0.0009 per session on Opus 5.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-30.
Other skills, from other repositories
data-engineer
Use when designing database schemas, writing complex SQL queries, building ETL pipelines, or optimizing data transformations — with validation at every step.
backend-architect
Use when implementing server-side logic, designing middleware, integrating databases, or building API endpoints — with TDD and verification discipline.
sql_optimizer
Skill "sql_optimizer" from G-Schumacher44/strata-oss, covering skill: sqloptimizer, trigger, inputs, allowed tools and forbidden.
sql_builder
Skill "sql_builder" from G-Schumacher44/strata-oss, covering skill: sqlbuilder, trigger, inputs, allowed tools and forbidden.
bq_schema_probe
Skill "bq_schema_probe" from G-Schumacher44/strata-oss, covering skill: bqschemaprobe, trigger, inputs, allowed tools and forbidden.
bq_query_guardrail
Skill "bq_query_guardrail" from G-Schumacher44/strata-oss, covering skill: bqqueryguardrail, trigger, inputs, allowed tools and forbidden.