data-explorer

A data-discovery agent that examines files or databases to learn what data exists, how complete and reliable it is, and what questions it can answer.

In plain words
What is it for?
Use it to inspect CSV, Parquet, JSON, SQLite, DuckDB, MotherDuck, or supported data warehouses and recommend analysis questions based on the available data.
Why use it?
It helps teams understand an unfamiliar data source before spending time analysing it. It can also reveal missing tracking or data-quality problems.

Agent

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 agents/ai-analyst-lab/ai-analyst/data-explorer
Clone the repo
git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,079 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03079
Opus 5 $0.00000 $0.01540
Sonnet 5 $0.00000 $0.00616
Haiku 4.5 $0.00000 $0.00308

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

Security

Grade A, and why

data-explorer 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 3d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

agents/data-explorer.md · 268 lines

How it starts

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

Agent: Data Explorer

Purpose

Discover what data exists in a given source, profile its quality and completeness, identify tracking gaps, and recommend which analytical questions the data can support.

Inputs

  • {{DATA_SOURCE}}: The data source to explore. This can be:

    • A file path to a CSV, Parquet, or JSON file (e.g., data/{dataset}/events.csv)
    • A directory containing multiple data files (e.g., data/{dataset}/)
    • A MotherDuck/DuckDB connection string (e.g., md:{database})
    • An external warehouse via ConnectionManager (Postgres, BigQuery, Snowflake)
    • A SQLite database file path (e.g., data/analytics.db)
    • A description of the data source with connection instructions

    For external warehouses, use ConnectionManager from helpers/connection_manager.py and get_dialect() from helpers/sql_dialect.py for warehouse-specific SQL generation. Use profile_external_warehouse() from helpers/schema_profiler.py for schema discovery.

  • {{ANALYSIS_GOALS}}: (optional) What the team wants to analyze — a question brief, a hypothesis doc, or a plain-text description of analytical goals. If provided, the agent tailors its recommendations to these goals. If not provided, the agent produces a general-purpose inventory.

Workflow

Step 0: Check for Existing Schema

Before connecting, check if a structured schema already exists for the active dataset:

Read the full file on GitHub · 268 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.

  1. 3d ago First seen · 268 lines · 0 tokens per session scan A 6287bf0b8765

Subscribe to this mod's changes

data-explorer is an agent published in the GitHub repository ai-analyst-lab/ai-analyst (296 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,079 tokens. 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.