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 khalilbenaz/claude-skills-collection --skill data-validation-helpergit clone --depth 1 https://github.com/khalilbenaz/claude-skills-collectionWrote 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/khalilbenaz/claude-skills-collection/data-validation-helper)<a href="https://agentmods.dev/skills/khalilbenaz/claude-skills-collection/data-validation-helper"><img src="https://agentmods.dev/badge/skills/khalilbenaz/claude-skills-collection/data-validation-helper/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/khalilbenaz/claude-skills-collection/data-validation-helper"><img src="https://agentmods.dev/badge/skills/khalilbenaz/claude-skills-collection/data-validation-helper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 160 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00061 | $0.02194 |
| Opus 5 | $0.00030 | $0.01097 |
| Sonnet 5 | $0.00012 | $0.00439 |
| Haiku 4.5 | $0.00006 | $0.00219 |
Grade A, and why
data-validation-helper scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST http://schema-registry:8081/compatibility/subjects/transactions-value/versions/latest \ How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Validation Helper
Workflow en 8 étapes
1. Inventaire et règles métier
- Lister chaque colonne : type attendu, nullabilité, plage (min/max), format (regex, pattern date), unicité, enum de valeurs autorisées.
- Documenter dans un fichier versionné (
expectations.yaml,schema.yamlouconftest.py). - Critère clé : distinguer règle bloquante (type incorrect, PK dupliquée) de warning tolerable (outlier statistique, valeur rare).
2. Schema validation — fail fast
JSON Schema (API REST) :
from jsonschema import validate, ValidationError
schema = {
"type": "object",
"properties": {
"user_id": {"type": "integer"},
"email": {"type": "string", "format": "email"},
"amount": {"type": "number", "minimum": 0}
},
"required": ["user_id", "email", "amount"]
}
try:
validate(instance=payload, schema=schema)
except ValidationError as e:
raise ValueError(f"Payload invalide : {e.message}")
Pydantic v2 (Python objects) :
from pydantic import BaseModel, field_validator
from decimal import Decimal
class Transaction(BaseModel):
user_id: int
amount: Decimal
currency: str
@field_validator("currency")
@classmethod
def check_currency(cls, v: str) -> str:
if v not in {"TND", "EUR", "USD"}:
raise ValueError(f"Devise inconnue : {v}")
return v
Pandera (DataFrames) :
import pandera as pa
schema = pa.DataFrameSchema({
"user_id": pa.Column(int, nullable=False),
"amount": pa.Column(float, pa.Check.ge(0)),
"status": pa.Column(str, pa.Check.isin(["pending","done","failed"]))
})
validated_df = schema.validate(df, lazy=True) # lazy=True collecte toutes les erreurs
3. Dimensions de qualité à mesurer
| Dimension | Métrique cible | Requête type |
|---|---|---|
| Complétude | % non-null ≥ 99 % | COUNT(*) - COUNT(col) > 0 |
| Unicité | doublons = 0 | COUNT(*) != COUNT(DISTINCT id) |
| Exactitude | valeurs dans plage | amount < 0 OR amount > 1e7 |
| Fraîcheur | lag ≤ SLA | MAX(updated_at) < NOW() - INTERVAL '2 hours' |
| Cohérence | FK valide | t.status = 'paid' AND t.paid_at IS NULL |
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.
- 8d ago First seen · 210 lines · 61 tokens per session scan A c06bcf17fa1d
data-validation-helper is a skill published in the GitHub repository khalilbenaz/claude-skills-collection (22 stars, last pushed 18d ago), licensed MIT. It adds 61 tokens to every session and 2,194 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
refactor
Refactors code for quality and maintainability. Triggers: refactor, clean up, restructure, improve code, modernize.
testing-patterns
Testing strategy: pyramid, AAA, mocks/fakes/stubs, flaky tests, coverage. Triggers: test, fixture, mock, stub, e2e, TDD, Playwright, Cypress, flaky, coverage, property-based.
unit-test
A Go testing workflow for writing unit tests: small tests that check individual functions or components. It supports table-driven cases, where many inputs and expected results are organised in one test, and subtests.
fuzzing-test
A Go testing guide for generating fuzz tests, which repeatedly try varied inputs to find crashes and unexpected behavior. It first checks whether the code is suitable for fuzzing.
testing-strategy
Comprehensive testing expertise across unit, integration, and e2e tests. Covers pytest, Vitest, Jest, Go testing, Playwright, Cypress. Test pyramids, TDD workflow, mocking patterns, coverage targets, property-based testing, snapshot testing, parameterized tests, fixtures, CI integration. Use when writing tests…
frappe-testing-unit
Use when writing unit tests, integration tests, creating test fixtures, or running tests with bench run-tests. Prevents flaky tests from missing fixtures, incorrect test isolation, and wrong test base classes. Covers frappe.tests.utils, IntegrationTestCase, UnitTestCase, test fixtures, bench run-tests flags, test…