validate

validate is a skill for Claude Code from bibinprathap/VeritasGraph. It costs 0 tokens per session (1,140 once invoked), scanned A, a copy of validate, MIT.

A checker for VeritasReason pipelines, extracted data, knowledge-graph structures, and ontologies. An ontology is a set of defined concepts and relationships used to organize information.

In plain words
What is it for?
Use it to validate pipelines, individual steps, dependencies, extraction results, graphs, and ontologies.
Why use it?
It helps find errors, warnings, missing dependencies, and inconsistencies before a reasoning workflow is used.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the veritasreason plugin — 17 skills, 3 agents, 2 hooks shipped together

Good fit Use it to validate pipelines, individual steps, dependencies, extraction results, graphs, and ontologies.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bibinprathap/veritasgraph/validate
Install

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.

Any agent
npx skills add bibinprathap/VeritasGraph --skill validate
Clone the repo
git clone --depth 1 https://github.com/bibinprathap/VeritasGraph

Made for: Claude Code.

Or install veritasreason, the plugin that ships this one along with the rest of its 17 skills, 3 agents, 2 hooks.

Wrote 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.

agentmods badge for validate

README.md
[![agentmods](https://agentmods.dev/badge/skills/bibinprathap/veritasgraph/validate/github.svg)](https://agentmods.dev/skills/bibinprathap/veritasgraph/validate)
Your own site
<a href="https://agentmods.dev/skills/bibinprathap/veritasgraph/validate"><img src="https://agentmods.dev/badge/skills/bibinprathap/veritasgraph/validate/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.

agentmods 80×15 button for validate

Your own site · 80×15
<a href="https://agentmods.dev/skills/bibinprathap/veritasgraph/validate"><img src="https://agentmods.dev/badge/skills/bibinprathap/veritasgraph/validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,140 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 94% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01140
Opus 5.5 $0.00000 $0.00456
Sonnet 5.5 $0.00000 $0.00228
Haiku 4.5 $0.00000 $0.00114

Measured 1mo ago against content hash 5acc6eec863f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

validate 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.

Origin

This is a copy

94% identical to validate — 36 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

veritas-reason/plugins/skills/validate/SKILL.md · 229 lines

How it starts

The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/veritasreason:validate

Validate pipeline and graph quality. Usage: /veritasreason:validate <target> [options]

$ARGUMENTS = target type + optional config or path.


pipeline [--config '<json>']

Validate a full pipeline builder configuration.

from veritasreason.pipeline.pipeline_builder import PipelineBuilder
from veritasreason.pipeline.pipeline_validator import PipelineValidator

builder = PipelineBuilder()
if config_json:
    import json
    builder.build_pipeline(json.loads(config_json))

# PipelineBuilder has its own quick validate
quick = builder.validate_pipeline()  # returns Dict

# PipelineValidator gives full ValidationResult(valid, errors, warnings)
# Does NOT raise — always returns a result object
validator = PipelineValidator()
result = validator.validate(builder)

# Also check inter-step dependencies
deps = validator.check_dependencies(builder)

Output:

Pipeline Validation:  VALID ✓  |  INVALID ✗
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Steps:    N registered
Valid:    M steps

Errors (K):
  ✗ [step_name] <error message>

Warnings (J):
  ⚠ [step_name] <warning message>

Dependencies:
  ✓ All dependencies resolved
  ✗ Step "<name>" depends on missing step "<dep>"

Result: <valid> — K errors, J warnings

step <step_name> [--type <type>] [--constraints '<json>']

Validate a single pipeline step.

from veritasreason.pipeline.pipeline_builder import PipelineBuilder
from veritasreason.pipeline.pipeline_validator import PipelineValidator
import json

builder = PipelineBuilder()
step = builder.get_step(step_name)

validator = PipelineValidator()
result = validator.validate_step(
    step=step,
    **json.loads(constraints_json) if constraints_json else {},
)

Output: same checklist format but scoped to a single step.


dependencies

Check all inter-step dependency resolution for the active pipeline.

from veritasreason.pipeline.pipeline_builder import PipelineBuilder
from veritasreason.pipeline.pipeline_validator import PipelineValidator

builder = PipelineBuilder()
validator = PipelineValidator()

deps = validator.check_dependencies(builder)

Read the full file on GitHub · 229 lines

Changes

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.

  1. 1mo ago First seen · 229 lines · 0 tokens per session scan A 5acc6eec863f

Subscribe to this mod's changes

validate is a skill published in the GitHub repository bibinprathap/VeritasGraph (325 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,140 tokens. A static security scan graded it A with 0 findings. It is 94% identical to validate, differing in 36 lines, and is treated as a copy.