speckit.validate

speckit.validate is a skill for Claude Code, Codex from compnew2006/Spec-Kit-Antigravity-Skills. It costs 12 tokens per session (594 once invoked), scanned A, original, no licence file.

A requirements check that compares an implementation with its written specification.

In plain words
What is it for?
Use it to review whether completed code matches the expected behaviour described in a specification.
Why use it?
It helps find missing or incorrectly implemented requirements before the work is considered complete.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing.

Good fit Use it to review whether completed code matches the expected behaviour described in a specification.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/compnew2006/spec-kit-antigravity-skills/speckit.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 compnew2006/Spec-Kit-Antigravity-Skills --skill speckit.validate
Clone the repo
git clone --depth 1 https://github.com/compnew2006/Spec-Kit-Antigravity-Skills

Made for: Claude Code, Codex.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/compnew2006/spec-kit-antigravity-skills/speckit.validate"><img src="https://agentmods.dev/badge/skills/compnew2006/spec-kit-antigravity-skills/speckit.validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 594 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 unknown 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.1 $0.00012 $0.00594
Opus 5.5 $0.00005 $0.00238
Sonnet 5.5 $0.00002 $0.00119
Haiku 4.5 $0.00001 $0.00059

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

Security

Grade A, and why

speckit.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 2mo 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.

skills/speckit.validate/SKILL.md · 94 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. 2mo ago First seen · 94 lines · 12 tokens per session scan A 20f7a3ae6338

Subscribe to this mod's changes

speckit.validate is a skill published in the GitHub repository compnew2006/Spec-Kit-Antigravity-Skills (73 stars, last pushed 9mo ago), with no licence file. It adds 12 tokens to every session and 594 once invoked, about $0.0000 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-30.

Related

Other skills, from other repositories

task-reviewer

A structured review process for checking task and verification-plan documents against project requirements. It models requirements, user stories, tasks, contracts, and the evidence needed to show that work is complete.

Haaaiawd/ANWS · 83 tokens

e2e-testing-guide

A guide for writing human-led end-to-end testing documents. End-to-end testing checks a product from the user’s point of view across complete tasks, while manual verification means a person performs the checks.

Haaaiawd/ANWS · 106 tokens

task-planner

A planning method that breaks a system design into a work breakdown structure, meaning a hierarchy of concrete tasks and dependencies. It produces an execution checklist and a separate verification plan in Chinese-language project documents.

Haaaiawd/ANWS · 51 tokens

writing-plans

Use when you have a spec or requirements for a multi-step task, before touching code.

Bilal140202/the-lord-of-the-skills · 21 tokens

gcp-qa

GCP QA and review persona. Critiques and evaluates designs, implementations, and release candidates against acceptance criteria. Owns linting, freshness checks, link validation, and smoke tests. Raises blockers before release. Quality gate authority for both the plugin itself and solutions built with it. Use when the…

jpantsjoha/googlecloud-plugin · 92 tokens

spec-driven-development

Spec-first workflow where an executable, testable specification is written before code and becomes the single source of truth that tests verify against, flowing spec → acceptance criteria → tasks → implementation.

andreibesleaga/GABBE · 40 tokens