codex-sdd:validate

A check that compares implemented code with an OpenSpec change and reports differences. It is the fourth phase of the OpenSpec workflow, after implementation tasks have been completed or started.

In plain words
What is it for?
Use it when asked to validate a change, check a specification, or investigate unexpected behaviour in an OpenSpec workflow.
Why use it?
It helps find drift between the planned design and the code, as well as missing change files, incomplete tasks, or outdated affected documentation.

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/skyloevil/codex-sdd/validate
Any agent
npx skills add skyloevil/codex-sdd --skill validate
Clone the repo
git clone --depth 1 https://github.com/skyloevil/codex-sdd

Made for: Claude Code, Codex.

Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 860 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.00029 $0.00860
Opus 5 $0.00015 $0.00430
Sonnet 5 $0.00006 $0.00172
Haiku 4.5 $0.00003 $0.00086

Measured yesterday against content hash 72e8024f0e9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

codex-sdd: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 yesterday.

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.

skills/validate/SKILL.md · 105 lines

How it starts

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

OpenSpec Validate

Context

Validate is the fourth phase of the OpenSpec workflow. It checks that the implementation aligns with the specification and identifies drift between the planned design and actual code. This is the "catch deviation early" step.

Trigger

Any of these patterns triggers this skill:

  • User says "openspec validate" or "openspec:validate"
  • User says "check spec" or "validate change"
  • All tasks are completed (state auto-transitions to validate)
  • User reports unexpected behavior during testing
  • openspec_get_status shows phase is validate

Prerequisites

  • All implementation tasks completed (or at least started)
  • active change artifacts exist under openspec/changes/<changeId>/

Workflow

Step 1: Run Validation

Call openspec_validate to get a programmatic drift report:

openspec_validate({})

This checks:

  • All active artifacts exist
  • All tasks are marked complete
  • Required hooks are complete
  • Completed tasks have structured validation evidence when the loop state is active

Also call docs_check_freshness for affected spec domains. Domain specs that do not include the active change should be treated as validation drift and fixed with openspec_sync_specs before archive.

Step 2: Manual Validation Checks

Beyond the automated checks, also verify:

Interface Alignment:

  • Do the implemented APIs match the design document?
  • Are request/response fields consistent with the spec?
  • Are error codes and edge cases handled?

Behavioral Coverage:

  • Are the main acceptance scenarios from the proposal covered?
  • Are edge cases handled (null inputs, empty states, timeouts)?
  • Are concurrency/locking behaviors correct?

Code Quality:

  • Are there any obvious issues (hard-coded values, security concerns)?
  • Are tests added for new functionality?

Record each concrete validation result with openspec_record_validation_evidence. Use evidence type test, lint, typecheck, manual, hook, spec_alignment, or ci. A task should not be treated as fully accepted until its required behavior has passed evidence or a human review explicitly accepts the gap.

Read the full file on GitHub · 105 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. yesterday First seen · 105 lines · 29 tokens per session scan A 72e8024f0e9a

Subscribe to this mod's changes

codex-sdd:validate is a skill published in the GitHub repository skyloevil/codex-sdd (1 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 860 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-08-31.

Related

Other skills, from other repositories

codexkit-repository-maintenance

Use when maintaining or improving the GameStudio-CodexKIT source repository, including CI, governance, catalog, generators, adapters, packaging, documentation, versioning, or release readiness.

hoatv2211/GameStudio-CodexKIT · 45 tokens

unity-ui-art-and-motion-production

Use when new or revised Unity UI visuals, icons, panels, 9-slice sprites, component states, HUD or menu layouts, popup motion, screen transitions, or flattened UI screenshot decomposition must be produced through Figma and integrated into uGUI, NGUI, or UI Toolkit; not for UI debugging, localization-only work…

hoatv2211/GameStudio-CodexKIT · 83 tokens

game-screenshot-showcase-and-store-packaging

Use when a Unity team needs approved PlayMode screenshots, immutable capture evidence, reviewed showcase slides, or report-only store screenshot packaging without auto-upload, signing, or submission.

hoatv2211/GameStudio-CodexKIT · 44 tokens

studio-project-scaffold

Use when running gamestudio init, status, or uninit, or bootstrapping a new or adopted game repository with AGENTS.md, HANDOFF.md, .agents/CONTRACT.md, project governance, a subsystem registry, or a per-project adapter report, plan digest, named reviewer, backup root, generated agent overlay, apply, uninstall, and…

hoatv2211/GameStudio-CodexKIT · 85 tokens

using-game-studio-skills

Use when starting any GameStudio-CodexKIT task or when a model runner is unavailable and someone requests a confidence-based PASS.

hoatv2211/GameStudio-CodexKIT · 33 tokens

skill-authoring-and-audit

Use when creating or revising a GameStudio-CodexKIT skill, resolving ambiguous skill triggers, auditing provenance or lifecycle maturity, or deriving reusable capabilities from session history.

hoatv2211/GameStudio-CodexKIT · 41 tokens