data-check

A data-quality check for financial information, covering missing values, unusual results, and inconsistencies.

In plain words
What is it for?
Use it to check a financial table for quality issues, or hand off to a more detailed data-quality analysis.
Why use it?
It helps find problems in financial data before they affect reports or decisions.

Command

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 commands/datarails/dr-claude-code-plugins-re/data-check
Clone the repo
git clone --depth 1 https://github.com/Datarails/dr-claude-code-plugins-re
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 165 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.00016 $0.00165
Opus 5 $0.00008 $0.00082
Sonnet 5 $0.00003 $0.00033
Haiku 4.5 $0.00002 $0.00016

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

Security

Grade A, and why

data-check 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 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.

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.

commands/data-check.md · 18 lines

What it actually says

Data Quality Check

This command is a thin launcher — the single maintained data-quality recipe lives in the datarails-financeos:anomalies skill. Do not improvise workflow steps here.

Invoke the datarails-financeos:anomalies skill with the user's arguments (a table name or id if they gave one; otherwise the skill discovers the financials table itself).

Related skills for the handoff:

  • Field-level statistical profiling (ranges, null rates, cardinality) → datarails-financeos:profile.
  • A full data-quality Excel workbook deliverable → datarails-financeos:anomalies-report.
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. 2d ago First seen · 18 lines · 16 tokens per session scan A 996291b8c9cc

Subscribe to this mod's changes

data-check is a command published in the GitHub repository Datarails/dr-claude-code-plugins-re (3 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 165 once invoked, about $0.0001 per session on Opus 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-31.