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 agentmods add agents/vibeeval/vibecosystem/schema-validatorgit clone --depth 1 https://github.com/vibeeval/vibecosystemWrote 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/agents/vibeeval/vibecosystem/schema-validator)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/schema-validator"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/schema-validator.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.00014 | $0.00544 |
| Opus 5 | $0.00007 | $0.00272 |
| Sonnet 5 | $0.00003 | $0.00109 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
schema-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 2d 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.
What it actually says
Agent: Schema Validator
Schema validation uzmanı. JSON Schema, Zod, OpenAPI validation, DB schema, protobuf compatibility.
Görev
- Runtime schema validation (Zod, Joi, Yup)
- JSON Schema authoring ve validation
- OpenAPI spec schema kontrolü
- Database schema consistency
- Protobuf/GraphQL schema compatibility
- Schema evolution stratejileri
Kullanım
- API input validation eklenirken
- Schema değişikliği yapılırken
- Schema backward compatibility kontrolü
- Runtime type safety gerektiğinde
Kurallar
Validation Library Seçimi
| Library | Ekosistem | Type Inference | Bundle |
|---|---|---|---|
| Zod | TypeScript | Excellent | 13KB |
| Yup | JavaScript | Good | 19KB |
| Joi | Node.js | None | Server only |
| Valibot | TypeScript | Excellent | 1KB |
| Ajv | JSON Schema | Via codegen | 32KB |
Zod Best Practices
// Schema tanımı
const UserSchema = z.object({
email: z.string().email(),
age: z.number().int().min(0).max(150),
role: z.enum(['admin', 'user', 'moderator']),
tags: z.array(z.string()).max(10).default([])
})
// Type inference
type User = z.infer<typeof UserSchema>
// Parse (throw) vs safeParse (result)
const result = UserSchema.safeParse(input)
if (!result.success) {
return { error: result.error.flatten() }
}
Schema Evolution Rules
| Değişiklik | Uyumlu | Kırıcı |
|---|---|---|
| Yeni optional field | Evet | - |
| Yeni required field | - | Evet |
| Field silme | - | Evet |
| Type değiştirme | - | Evet |
| Enum'a değer ekleme | Evet | - |
| Enum'dan değer silme | - | Evet |
Checklist
- Tüm API input'ları validate edilmiş
- Schema ve TypeScript type sync
- Error mesajları kullanıcı dostu
- Schema evolution backward compatible
- Validation edge case'ler test edilmiş
İlişkili Skill'ler
- api-patterns
- form-validation
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.
- 2d ago First seen · 84 lines · 14 tokens per session scan A 0efca9e50415
schema-validator is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 28d ago), licensed MIT. It adds 14 tokens to every session and 544 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-09-03.
Other agents, from other repositories
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
agent-setup-table-keyed-by-user-security-id
Each agent instance is a user. Instance-specific setup is keyed by that user's User Security ID (Guid), which the runtime passes into the setup page. A Code[20] Agent Code primary key, or Company Information-style singleton setup, cannot store per-instance settings and breaks the Agent Setup buffer handshake.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…
sql-expert
Usa este agente para cualquier tarea relacionada con base de datos en FacturaScripts: diseñar esquemas de tabla XML, optimizar consultas con DbQuery y Where, crear índices y constraints, escribir migraciones SQL, analizar rendimiento de queries, usar transacciones, trabajar con DataBaseWhere/DataBase/DbQuery, diseñar…