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 skills add skyloevil/codex-sdd --skill validategit clone --depth 1 https://github.com/skyloevil/codex-sddWrote 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/skills/skyloevil/codex-sdd/validate)<a href="https://agentmods.dev/skills/skyloevil/codex-sdd/validate"><img src="https://agentmods.dev/badge/skills/skyloevil/codex-sdd/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.
<a href="https://agentmods.dev/skills/skyloevil/codex-sdd/validate"><img src="https://agentmods.dev/badge/skills/skyloevil/codex-sdd/validate.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.00029 | $0.00860 |
| Opus 5.5 | $0.00012 | $0.00344 |
| Sonnet 5.5 | $0.00006 | $0.00172 |
| Haiku 4.5 | $0.00003 | $0.00086 |
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 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 — 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_statusshows phase isvalidate
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.
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 · 105 lines · 29 tokens per session scan A 72e8024f0e9a
codex-sdd:validate is a skill published in the GitHub repository skyloevil/codex-sdd (1 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 860 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-08-31.
Other skills, from other repositories
code-intelligence-contract
Use when dependency, call-chain, blast-radius, architecture, domain-flow, or unfamiliar-codebase analysis needs an optional vendor-neutral code-intelligence provider.
review-swarm
Use when reviewing a known change set through parallel read-only code, architecture, test, safety, or product lanes with disjoint concerns and one integrator verdict.
lua-client-server-contract-audit
Use when normalized Lua client/server RPC contract copies or generated protocol tables disagree on opcode, request-response fields, types, ordering, or source authority.
mmorpg-packet-protocol-review
Use when a C++ server and Unity client protocol manifest or wire compatibility review covers packet version negotiation, numeric opcode registry, byte layout order, direction, and request-response pairing.
review-code
Read code. Understand it. Find issues. Report clearly.
do-it-audit
Use when the user explicitly requests a deep repository or scoped audit; not for ordinary diff review.