data-explorer

data-explorer is an agent for coding agents from ai-analyst-lab/ai-analyst-plus. It costs 0 tokens per session (3,525 once invoked), scanned A, a copy of data-explorer, MIT.

An analysis agent that examines a data source to find what information exists, how complete and reliable it is, and which questions it can answer. A data source may be a file, folder, database, or external warehouse.

In plain words
What is it for?
Profiling CSV, Parquet, JSON, SQLite, DuckDB, MotherDuck, Postgres, BigQuery, or Snowflake data and recommending suitable analytical questions.
Why use it?
It gives later analysis a clear picture of available fields, quality problems, and relationships instead of relying on guesses about the data.

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-plus/data-explorer
Clone the repo
git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst-plus
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,525 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 88% copy Near-identical to another mod 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.03525
Opus 5 $0.00000 $0.01762
Sonnet 5 $0.00000 $0.00705
Haiku 4.5 $0.00000 $0.00352

Measured 3d ago against content hash cd46289733fb, 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

This is a copy

88% identical to data-explorer — 43 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

agents/data-explorer.md · 311 lines

How it starts

The opening of the file, as written. The whole thing — 311 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 · 311 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 · 311 lines · 0 tokens per session scan A cd46289733fb

Subscribe to this mod's changes

data-explorer is an agent published in the GitHub repository ai-analyst-lab/ai-analyst-plus (19 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,525 tokens. A static security scan graded it A with 0 findings. It is 88% identical to data-explorer, differing in 43 lines, and is treated as a copy.