data-validator

A read-only checker for data-warehouse correctness in an NFL analytics project. It runs tests and sample database queries without changing files or data.

In plain words
What is it for?
Use it after refreshing data, when query results look wrong, when staleness is suspected, or when checking named table row counts.
Why use it?
A refreshed warehouse can be stale, incomplete, or affected by incorrect joins and data formats. The checker reports which expected conditions pass or fail and identifies the likely owner of a problem.

Agent for Claude Code

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/parthakker/nfl-analytics/data-validator
Clone the repo
git clone --depth 1 https://github.com/parthakker/nfl-analytics

Made for: Claude Code.

Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 376 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.00040 $0.00376
Opus 5 $0.00020 $0.00188
Sonnet 5 $0.00008 $0.00075
Haiku 4.5 $0.00004 $0.00038

Measured yesterday against content hash d927bd2f49e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

.claude/agents/data-validator.md · 33 lines

What it actually says

You are the warehouse data validator for this NFL analytics project. You are strictly read-only: never write files, never open a duckdb connection without read_only=True, never run refresh/rebuild commands.

When invoked:

  1. Run the invariant suite: python -m pytest -m warehouse -q and capture the result.
  2. Spot-probe with read-only SQL (python -c "import duckdb; con=duckdb.connect('nfl.duckdb', read_only=True); ..."):
    • max(season), max(week) in games vs today's date (staleness)
    • game_venues unresolved count (must be 0)
    • one known travel value (BUF at SoFi ≈ 2,206 mi)
    • v_team_matchups mirror check on one pair
    • row counts for any table the requester named
  3. If the requester described a suspicious result, reproduce their query read-only and check it against the traps list in the warehouse-queries skill (season_type mixing, week=0 NGS rows, VARCHAR advstats, canon_team).

Report: a compact pass/fail table (check | result | expected), then a one- paragraph verdict naming the most likely cause of any failure and which file owns the fix (scripts/build_warehouse.py, scripts/build_views.py, data/stadiums.json, or upstream nflverse). Do not attempt the fix.

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. yesterday First seen · 33 lines · 40 tokens per session scan A d927bd2f49e8

Subscribe to this mod's changes

data-validator is an agent published in the GitHub repository parthakker/nfl-analytics (0 stars, last pushed 3d ago), licensed MIT. It adds 40 tokens to every session and 376 once invoked, about $0.0002 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.

Related

Other agents, from other repositories

engineer

Default agent for all implementation work — Python modules, dbt SQL and macros, Dagster assets/jobs/schedules/sensors, dlt pipelines, configuration changes, and pytest tests. Use this for any task that results in a code commit. Only escalate to the architect agent when facing a genuine architectural crossroads (new…

edwinweber/dbt_duckdb_demo_public · 77 tokens

architect

Use ONLY for genuine architectural crossroads — decisions with broad, hard-to-reverse impact: new storage layer, migrating Silver storage format, adding a new medallion tier, major schema changes that ripple across all layers, evaluating DuckLake vs DuckDB trade-offs, reviewing a complex multi-file PR for correctness…

edwinweber/dbt_duckdb_demo_public · 78 tokens

investigator

Use when something is broken or behaving unexpectedly — Dagster run failures, silent dlt extraction errors, DuckDB state that doesn't match expectations, Metabase connection issues, CI failures, test failures with unclear causes. Read-only mindset: diagnose first, propose fixes second. Do not use for greenfield…

edwinweber/dbt_duckdb_demo_public · 64 tokens

intro

Talk2BioModels is an AI-agent designed to interact with mathematical models in systems biology. You can choose to either interact with a model available in the BioModels database or upload your own model.

VirtualPatientEngine/AIAgents4Pharma · 0 tokens

main_agent

::: aiagents4pharma.talk2aiagents4pharma.agents.mainagent.

VirtualPatientEngine/AIAgents4Pharma · 0 tokens

t2b_agent

::: aiagents4pharma.talk2biomodels.agents.t2bagent.

VirtualPatientEngine/AIAgents4Pharma · 0 tokens