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 saajunaid/caddis-plugin --skill data-validationgit clone --depth 1 https://github.com/saajunaid/caddis-pluginWrote 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/saajunaid/caddis-plugin/data-validation)<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/data-validation"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/data-validation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/data-validation"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/data-validation.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.01770 |
| Opus 5.5 | $0.00014 | $0.00708 |
| Sonnet 5.5 | $0.00007 | $0.00354 |
| Haiku 4.5 | $0.00003 | $0.00177 |
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 29d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Validation Skill
Bad data in → bad decisions out. Validate at every boundary: ingestion, transformation, and output.
1. When to Apply This Skill
Trigger conditions:
- Building or reviewing ETL/ELT pipelines
- "How do we validate incoming data?"
- Designing data contracts between services
- Data quality issues in production
- Schema migration or new data source integration
2. Validation Layers
Validate at three boundaries — not just one.
Source → [Ingestion Validation] → Raw Layer
Raw → [Transform Validation] → Clean Layer
Clean → [Output Validation] → Consumer / API / Report
| Layer | What to Check | Fail Strategy |
|---|---|---|
| Ingestion | Schema, types, required fields, file format | Reject row or file, log to dead-letter |
| Transform | Business rules, referential integrity, ranges | Flag row, route to review queue |
| Output | Final shape matches consumer contract | Block publish, alert team |
3. Pydantic Validation (Python)
Schema Definition
from pydantic import BaseModel, Field, field_validator, model_validator
from datetime import date
from enum import Enum
class Priority(str, Enum):
LOW = "low"
MEDIUM = "medium"
HIGH = "high"
CRITICAL = "critical"
class ComplaintRecord(BaseModel):
complaint_id: str = Field(..., min_length=1, max_length=50)
customer_id: str = Field(..., pattern=r"^CUST-\d{6}$")
category: str = Field(..., min_length=1)
priority: Priority
description: str = Field(..., min_length=10, max_length=5000)
created_date: date
resolved_date: date | None = None
amount: float = Field(default=0, ge=0, le=1_000_000)
@field_validator("resolved_date")
@classmethod
def resolved_after_created(cls, v, info):
if v and info.data.get("created_date") and v < info.data["created_date"]:
raise ValueError("Resolved date cannot be before created date")
return v
@model_validator(mode="after")
def critical_must_have_description(self):
if self.priority == Priority.CRITICAL and len(self.description) < 50:
raise ValueError("Critical complaints require detailed description (50+ chars)")
return self
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.
- 29d ago Changed · -19 tokens per session 23ede9971335
- 1mo ago First seen · 221 lines · 54 tokens per session scan A ca620bd220d7
data-validation is a skill published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 1,770 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
supabase
Skill "supabase" from dhaupin/vant, covering supabase, when to use, what to do, 1. connect and supabase-js.
discover-source
Discover a data source (REST API, Postgres, MySQL, or local file) and register it with Elliot so its tables and endpoints become queryable. Use as the first step of building a new connector.
Django Web框架
A guide for developing Django applications, using a Python web framework for websites and APIs.
分布式一致性
A guide for keeping data coordinated across multiple computers or services. Distributed consistency covers how systems synchronize data and handle conflicting updates.
仓储
A persistence abstraction for aggregates, which are groups of related business objects treated as one unit. It hides database access so the domain layer does not depend on a specific storage technology.
事件溯源
A way to store each change to a system as a permanent event instead of storing only the latest state. The current state can be rebuilt by replaying those events.