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.
npx skills add zpower426/datapowers --skill data-validationgit clone --depth 1 https://github.com/zpower426/datapowersWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/zpower426/datapowers/data-validation)<a href="https://agentmods.dev/skills/zpower426/datapowers/data-validation"><img src="https://agentmods.dev/badge/skills/zpower426/datapowers/data-validation.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00028 | $0.01682 |
| Opus 5 | $0.00014 | $0.00841 |
| Sonnet 5 | $0.00006 | $0.00336 |
| Haiku 4.5 | $0.00003 | $0.00168 |
Grade A, and why
data-validation 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Validation
Schema-based and statistical validation of datasets before any downstream use.
Iron Law: NO TRAINING WITHOUT DATA QUALITY VALIDATION
Checklist
- Define or load schema — column names, dtypes, nullable flags, value ranges
- Run structural checks — shape, columns present, no unexpected columns
- Run type checks — each column matches expected dtype
- Run range checks — numeric columns within expected bounds
- Run categorical checks — only expected categories present
- Run null checks — nullability constraints satisfied
- Run statistical checks — distributions within expected drift thresholds
- Run cross-column checks — logical constraints between columns
- Generate validation report — pass/fail per check, severity, action
- Gate decision — BLOCK if any CRITICAL failure, WARN for others
Validation Framework
Use Pandera for Python-based schema validation:
import pandera as pa
from pandera.typing import DataFrame, Series
class CustomerSchema(pa.DataFrameModel):
age: Series[int] = pa.Field(ge=0, le=120, nullable=False)
income: Series[float] = pa.Field(ge=0.0, nullable=True)
churn: Series[int] = pa.Field(isin=[0, 1], nullable=False)
signup_date: Series[pa.DateTime] = pa.Field(nullable=False)
class Config:
coerce = True
strict = True # no extra columns allowed
# Validate
try:
CustomerSchema.validate(df, lazy=True)
print("✅ Validation passed")
except pa.errors.SchemaErrors as e:
print("❌ Validation failed:")
print(e.failure_cases)
Structural Checks
# Required columns present
expected_cols = set(schema.columns.keys())
actual_cols = set(df.columns)
missing = expected_cols - actual_cols
extra = actual_cols - expected_cols
if missing:
print(f"❌ CRITICAL: Missing columns: {missing}")
if extra:
print(f"⚠️ WARN: Unexpected columns: {extra}")
# Row count sanity
if len(df) == 0:
raise ValueError("❌ CRITICAL: Dataset is empty")
if len(df) < min_expected_rows:
print(f"⚠️ WARN: Only {len(df)} rows, expected at least {min_expected_rows}")
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.
- 7d ago First seen · 205 lines · 28 tokens per session scan A f74d89af6416
data-validation is a skill published in the GitHub repository zpower426/datapowers (1 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 1,682 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.
Other skills, from other repositories
local-llm
A setup and control layer for running language models locally on a Mac with Apple silicon, so data can stay on the computer.
llm-app-patterns
Production-ready patterns for building LLM applications. Covers RAG pipelines, agent architectures, prompt IDEs, and LLMOps monitoring. Use when designing AI applications, implementing RAG, building agents, or setting up LLM observability.
blip-2-vision-language
Vision-language pre-training framework bridging frozen image encoders and LLMs. Use when you need image captioning, visual question answering, image-text retrieval, or multimodal chat with state-of-the-art zero-shot performance.
grpo-rl-training
Expert guidance for GRPO/RL fine-tuning with TRL for reasoning and task-specific model training.
knowledge-distillation
Compress large language models using knowledge distillation from teacher to student models. Use when deploying smaller models with retained performance, transferring GPT-4 capabilities to open-source models, or reducing inference costs. Covers temperature scaling, soft targets, reverse KLD, logit distillation, and…
speculative-decoding
Accelerate LLM inference using speculative decoding, Medusa multiple heads, and lookahead decoding techniques. Use when optimizing inference speed (1.5-3.6× speedup), reducing latency for real-time applications, or deploying models with limited compute. Covers draft models, tree-based attention, Jacobi iteration…