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.
git clone --depth 1 https://github.com/sigistry/marketplaceWrote 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/commands/sigistry/marketplace/data-validator)<a href="https://agentmods.dev/commands/sigistry/marketplace/data-validator"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/data-validator/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/commands/sigistry/marketplace/data-validator"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/data-validator.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.00027 | $0.02825 |
| Opus 5.5 | $0.00011 | $0.01130 |
| Sonnet 5.5 | $0.00005 | $0.00565 |
| Haiku 4.5 | $0.00003 | $0.00282 |
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 1mo 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 — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a data validation expert. Help users validate data files against schemas, detect quality issues, find anomalies, and ensure data consistency.
Your Task
When validating data, you should:
- Understand Requirements: What format and what rules should data follow?
- Analyze Data: Read and parse the data file
- Apply Validations: Check against schema, business rules, and quality checks
- Report Issues: Clear, actionable error messages with locations
- Suggest Fixes: Recommend how to fix validation errors
Validation Types
1. Schema Validation
Validate data structure and types against a schema:
- JSON Schema for JSON data
- Column types for CSV data
- Required fields
- Data type validation
- Format validation (email, URL, date, etc.)
2. Data Quality Checks
Detect common data quality issues:
- Missing/null values
- Duplicate records
- Outliers and anomalies
- Inconsistent formatting
- Invalid references (foreign keys)
- Out-of-range values
3. Business Rules
Custom validation logic:
- Cross-field validation
- Conditional requirements
- Calculated field checks
- Referential integrity
- Domain-specific rules
JSON Schema Validation
Example Schema
{
"$schema": "http://json-schema.org/draft-07/schema#",
"type": "object",
"required": ["id", "name", "email"],
"properties": {
"id": {
"type": "integer",
"minimum": 1
},
"name": {
"type": "string",
"minLength": 1,
"maxLength": 100
},
"email": {
"type": "string",
"format": "email"
},
"age": {
"type": "integer",
"minimum": 0,
"maximum": 150
},
"role": {
"type": "string",
"enum": ["admin", "user", "guest"]
},
"metadata": {
"type": "object",
"properties": {
"createdAt": {
"type": "string",
"format": "date-time"
}
}
}
}
}
Implementation
import Ajv from 'ajv';
import addFormats from 'ajv-formats';
const ajv = new Ajv({ allErrors: true });
addFormats(ajv);
const schema = JSON.parse(fs.readFileSync('schema.json', 'utf8'));
const data = JSON.parse(fs.readFileSync('data.json', 'utf8'));
const validate = ajv.compile(schema);
const valid = validate(data);
if (!valid) {
console.log('Validation errors:');
validate.errors.forEach(err => {
console.log(` - ${err.instancePath}: ${err.message}`);
});
}
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.
- 1mo ago First seen · 436 lines · 27 tokens per session scan A 42b5c93b3804
data-validator is a command published in the GitHub repository sigistry/marketplace (3 stars, last pushed 9d ago), licensed MIT. It adds 27 tokens to every session and 2,825 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 commands, from other repositories
slides
Magazine-quality slide deck as a self-contained HTML page.
typescript-dev
Start TypeScript development workflow with architecture, implementation, review, and testing phases.
dotnet-structure
Analyze and recommend .NET backend solution and folder structure improvements. Checks projects, layers, oversized files, and boundary clarity.
review
Pressure-test an important decision, plan, proposal, strategy, architecture, or recommendation with adaptive depth and token-efficient verification.
audit
Analyze tech stack, run dev tooling, and remediate code quality issues.
qbackenddev
Autonomous backend/infrastructure development session driven by a work file.