All plugins

dataprobe

Exact, local structure and quality checks over large CSV/TSV and JSONL data files that don't fit in a model's context. data_profile reports per-column inferred type, null rate, distinct count, numeric statistics and top values (for JSONL, the inferred union schema with per-field presence); data_validate reports only the actionable problems — mixed-type columns with the offending line numbers, ragged rows, duplicate rows, non-unique key candidates, constant or all-empty columns and malformed JSONL lines; data_head returns a clean parsed preview that handles quoted CSV and JSON correctly. Streamed, standard library only: no network, no credentials, no third-party dependencies, no self-update. Disclosure: reads the local data path you pass it (read-only) and honours Hermes' core read denylist.

rodricksz4h5Toolsv1.0.1Updated 7 days ago

About

Exact, local structure and quality checks over large CSV/TSV and JSONL data files that don't fit in a model's context. data_profile reports per-column inferred type, null rate, distinct count, numeric statistics and top values (for JSONL, the inferred union schema with per-field presence); data_validate reports only the actionable problems — mixed-type columns with the offending line numbers, ragged rows, duplicate rows, non-unique key candidates, constant or all-empty columns and malformed JSONL lines; data_head returns a clean parsed preview that handles quoted CSV and JSON correctly. Streamed, standard library only: no network, no credentials, no third-party dependencies, no self-update. Disclosure: reads the local data path you pass it (read-only) and honours Hermes' core read denylist.

dataprobe

Exact, local structure and quality checks over large data files, as three Hermes
tools. A language model can't read a 2 GB CSV or a million-line JSONL dataset, and
asked "is this data clean?" it will guess from the handful of rows it can see.
dataprobe streams the file on disk and returns ground truth: the real schema,
per-column statistics, and the specific rows that are wrong.

Why a tool and not a prompt or skill

The answers are computed over the whole file — the column that is 99% integer
with 143 stray strings on lines you can name, the duplicate primary keys, the
JSONL field that is present in only 82% of records. None of that is visible in a
sampled preview, and a skill that just instructs the model cannot produce it
reliably. It is also dependency-free: unlike pandas-based tooling it pulls in
nothing and downloads nothing.

Tools

data_profile

Full picture of a CSV/TSV or JSONL file.

argtyperequireddefaultmeaning
pathstringyes—local data file
formatstringnoautoforce csv | tsv | jsonl
top_valuesintegerno10top-N values per column (cap 100)
max_rowsintegerno2000000scan at most this many rows

CSV/TSV returns row count, column count, duplicate rows, ragged rows, and for
each column: inferred type, null count/percent, distinct count, a type breakdown,
top values, numeric min/max/mean/stdev/median/p25/p75, and
minority_type_lines — the line numbers of values that don't match the column's
dominant type.

JSONL returns the record count, parse errors with line numbers, and the
inferred union schema: every field with its presence percentage, type
distribution, whether it is optional, and example values.

data_validate

Only the actionable problems — use it to gate whether the agent should trust a file.

argtyperequireddefaultmeaning
pathstringyes—local data file
formatstringnoautoforce csv | tsv | jsonl
keystringno—column/field to check for uniqueness
max_rowsintegerno2000000scan at most this many rows

Flags: mixed_column_type / mixed_field_type (with offending line numbers),
ragged_rows, duplicate_rows, constant_column, all_empty_column,
optional_field, malformed_json_lines, non_object_records, and — when key
is given — key_not_unique / key_not_found.

data_head

First N parsed records as clean structured rows, correctly handling quoted
CSV fields and JSON objects (a raw byte head mangles both).

argtyperequireddefaultmeaning
pathstringyes—local data file
formatstringnoautoforce csv | tsv | jsonl
nintegerno10records to return (cap 1000)
columnsarrayno—only include these columns/fields

All three always return a JSON string; a bad path, blocked path or malformed
input returns { "ok": false, "error": "..." } rather than raising.

Format detection

.jsonl / .ndjson, or a first non-blank line that parses as a JSON object, is
treated as JSONL. .tsv is tab-delimited. Otherwise the CSV delimiter is sniffed
from a sample (, \t ; |). A UTF-8 BOM is handled and noted. Pass format to
override.

Safety and disclosure

  • Reads only the file path you pass, read-only. Never writes, deletes, or
    touches any other path.
  • Honours Hermes' read denylist. Inside the agent, every path is passed
    through the same check Core's read_file uses, so credential stores, internal
    caches and .env files are refused — dataprobe can't be used to read what the
    host protects.
  • Regular files only. Like Core's read_file, paths under /proc and /dev
    (including symlinks that resolve there) are refused, and so is anything that
    isn't a regular file — FIFOs, sockets and devices — before the file is opened.
  • No network, no credentials, no telemetry, no background processes, no
    self-update. Standard library only
    (csv, json, statistics).
  • A single call stops after 2,000,000 rows, truncates cells over 50,000 chars,
    and caps per-column distinct tracking at 10,000 — all flagged in the result —
    so runtime and memory stay bounded. A CSV field longer than 200,000 characters
    can't be parsed and returns an error instead.

Install

hermes plugins install rodricksz4h5/dataprobe

License

MIT — see LICENSE.

README from the reviewed commit 20d5190; it updates when the author re-pins.

More by rodricksz4h5

8 plugins by rodricksz4h5 in the catalog.

rodricksz4h5covsiftExact, local analysis of code coverage reports: LCOV (c8, nyc, Jest, Vitest, cargo-llvm-cov, lcov), Cobertura XML (coverage.py, Jest/Vitest, coverlet, gcovr, PHPUnit), JaCoCo XML, Clover XML, SonarQube generic XML, coverage.py, gcovr and Coveralls JSON, and Go cover profiles, from one file or a directory of them. coverage_diff takes a unified diff (git diff) and returns the added lines no test ran, per file, with diff coverage and an optional fail_under gate; coverage_summary gives exact line, branch and Go statement coverage, the least covered files with their uncovered lines and a per-directory rollup; coverage_file lists one file's uncovered lines and partial branches; coverage_compare shows which files lost coverage between two runs. Standard library only: no network, no credentials, no subprocess (never runs git or tests; the diff is passed in), no third-party dependencies, no self-update; XML entity declarations are refused. Disclosure: reads the local report and diff paths you pass it (read-only), only regular files, and honours Hermes' core read denylist.Communitytoolsrodricksz4h5layersiftExact, local reading of saved container images: docker save and podman save tars (classic and Docker 25+ layouts) and OCI image archives, including multi-platform indexes and gzip, bzip2 or xz compression. image_summary says where the size goes: each layer with the Dockerfile instruction that made it, the final filesystem size, bytes still shipped after a later layer deletes or overwrites them (which layer added them, which removed them), caches and archives left behind (apt lists, apk/yum/dnf, pip/uv/npm/yarn, Go and Cargo caches, temp directories, .git, compilers) with the fix, and the biggest directories and files; image_layer opens one layer; image_compare compares two images before and after a Dockerfile change. Standard library only: no network, never runs docker or contacts a registry, no credentials, no subprocess, never extracts to disk, no third-party dependencies, no self-update. Disclosure: reads the local image archives you pass it (read-only), only regular files, and honours Hermes' core read denylist.Communitytoolsrodricksz4h5locksiftExact, local review of dependency lockfiles: npm package-lock.json, pnpm-lock.yaml, yarn.lock (v1 and Berry), uv.lock, poetry.lock, Pipfile.lock, Cargo.lock, composer.lock, Gemfile.lock and go.sum. lock_diff compares two versions of a lockfile (a branch against main) and returns the dependency changes instead of thousands of lines of churn, with supply-chain signals per installed copy: a source that moved (registry to git or URL, another registry host, a different tarball or commit at the same version, an alias or patch that changed, a tarball that belongs to another package), checksums changed, removed or weakened, new install scripts, new registries. lock_summary gives counts, packages at several versions, non-registry sources and install scripts; lock_why shows the dependency chains that pull a package in. Standard library only: no network, no credentials, no subprocess (never runs git or a package manager), no third-party dependencies, no self-update. Disclosure: reads the local lockfile paths you pass it (read-only), only regular files, and honours Hermes' core read denylist.Communitytoolsrodricksz4h5logmineExact, local intelligence over large text log files. log_summarize mines the file into recurring message templates (masking numbers, IPs, UUIDs, hashes, quoted strings and timestamps so near-identical lines collapse into one ranked pattern with an exact count), plus a level histogram and the detected time span; log_grep is regex search with line numbers and grep-style context; log_timeline buckets events per minute/hour/day to find spikes. Streamed, so a log too big to fit in the model's context still works. Standard library only: no network, no credentials, no background processes, no self-update. Disclosure: reads the local log path you pass it (read-only).Communitytools

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section