validate

A validation workflow for checking specifications, files, implementations, project rules, two artifacts against each other, or whether an understanding is correct.

In plain words
What is it for?
Use it to validate a specification or file, check specification-to-code drift, compare artifacts, enforce project rules, or sanity-check an interpretation.
Why use it?
It helps identify quality issues, rule violations, and differences between what was requested and what was built.

Skill for Claude CodeCodex

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.

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

Made for: Claude Code, Codex.

Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,081 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00077 $0.01081
Opus 5 $0.00039 $0.00541
Sonnet 5 $0.00015 $0.00216
Haiku 4.5 $0.00008 $0.00108

Measured 2d ago against content hash 2b6a0fc0a705, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

plugins/start/skills/validate/SKILL.md · 134 lines

How it starts

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

Persona

Act as a validation orchestrator that ensures quality and correctness across specifications, implementations, and governance.

Validation Request: $ARGUMENTS

Interface

Finding { status: PASS | WARN | FAIL severity: HIGH | MEDIUM | LOW title: string // max 40 chars location: string // file:line issue: string // one sentence recommendation: string // how to fix }

State { target = $ARGUMENTS validationMode: Spec | File | Drift | Constitution | Comparison | Understanding perspectives = [] // from reference/perspectives.md mode: Standard | Agent Team findings: Finding[] }

Constraints

Always:

  • Delegate all validation tasks to specialist agents.
  • Launch ALL applicable validation perspectives simultaneously.
  • Include file paths and line numbers for all findings.
  • Every finding must have a clear, actionable fix recommendation.
  • Advisory by default — provide recommendations without blocking.

Never:

  • Validate code yourself — always delegate to specialist agents.
  • Skip constitution L1/L2 violations — these are blocking.
  • Present findings without specific file:line references.
  • Summarize agent findings — present complete results.

Reference Materials

  • reference/perspectives.md — perspective definitions, activation rules, mode-to-perspective mapping
  • reference/3cs-framework.md — completeness, consistency, correctness validation
  • reference/ambiguity-detection.md — vague language patterns and scoring
  • reference/drift-detection.md — spec-implementation alignment checking
  • reference/constitution-validation.md — governance rule enforcement
  • reference/output-format.md — assessment level definitions, next-step options
  • examples/output-example.md — concrete example of expected output format

Workflow

1. Parse Mode

Determine validation mode from $ARGUMENTS:

match (target) { /^\d{3}/ => Spec Validation file path => File Validation "drift" | "check drift" => Drift Detection "constitution" => Constitution Validation "$X against $Y" => Comparison Validation freeform text => Understanding Validation }

Read the full file on GitHub · 134 lines

Files

What ships with it

7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago First seen · 134 lines · 77 tokens per session scan A 2b6a0fc0a705

Subscribe to this mod's changes

validate is a skill published in the GitHub repository rsmdt/the-startup (510 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 1,081 once invoked, about $0.0004 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-08-30.

Related

Other skills, from other repositories

postgres-database-migration

Use this skill for planning, testing, and safely executing PostgreSQL schema migrations — especially when working with production data or shared databases. Trigger when user asks to: Test a schema migration before applying it to production Add, remove, or rename columns safely on a live table Change a column's data…

timescale/pg-aiguide · 222 tokens

setup-timescaledb-hypertables

Use this skill when creating database schemas or tables for Timescale, TimescaleDB, TigerData, or Tiger Cloud, especially for time-series, IoT, metrics, events, or log data. Use this to improve the performance of any insert-heavy table. Trigger when user asks to: Create or design SQL schemas/tables AND…

timescale/pg-aiguide · 219 tokens

design-postgis-tables

Comprehensive PostGIS spatial table design reference covering geometry types, coordinate systems, spatial indexing, and performance patterns for location-based applications.

timescale/pg-aiguide · 31 tokens

migrate-postgres-tables-to-hypertables

Use this skill to migrate identified PostgreSQL tables to Timescale/TimescaleDB hypertables with optimal configuration and validation. Trigger when user asks to: Migrate or convert PostgreSQL tables to hypertables Execute hypertable migration with minimal downtime Plan blue-green migration for large tables Validate…

timescale/pg-aiguide · 181 tokens

pgvector-semantic-search

Use this skill for setting up vector similarity search with pgvector for AI/ML embeddings, RAG applications, or semantic search. Trigger when user asks to: Store or search vector embeddings in PostgreSQL Set up semantic search, similarity search, or nearest neighbor search Create HNSW or IVFFlat indexes for vectors…

timescale/pg-aiguide · 190 tokens

find-hypertable-candidates

Use this skill to analyze an existing PostgreSQL database and identify which tables should be converted to Timescale/TimescaleDB hypertables. Trigger when user asks to: Analyze database tables for hypertable conversion potential Identify time-series or event tables in an existing schema Evaluate if a table would…

timescale/pg-aiguide · 184 tokens