spec-kit-analyze-consistency

spec-kit-analyze-consistency is a skill for Claude Code from ErikaAX08/erikas-skills. It costs 97 tokens per session (4,017 once invoked), scanned A, original, MIT.

A read-only checker that compares a feature's specification, technical plan, and task list. It reports missing coverage, disconnected tasks, postponed safety work, incomplete user stories, and unchecked safeguards.

In plain words
What is it for?
Use it to review spec.md, plan.md, and tasks.md and produce a consistency report with blocking or advisory findings. It also gives a READYFOREXECUTION verdict.
Why use it?
It shows whether planned work is complete and consistent before developers start implementing it. This helps reveal problems without changing the source documents.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions Claude Code.

Good fit Use it to review spec.md, plan.md, and tasks.md and produce a consistency report with blocking or advisory findings. It also gives a READYFOREXECUTION verdict.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/erikaax08/erikas-skills/spec-kit-analyze-consistency
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 ErikaAX08/erikas-skills --skill spec-kit-analyze-consistency
Clone the repo
git clone --depth 1 https://github.com/ErikaAX08/erikas-skills

Made for: Claude Code.

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 spec-kit-analyze-consistency

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/erikaax08/erikas-skills/spec-kit-analyze-consistency"><img src="https://agentmods.dev/badge/skills/erikaax08/erikas-skills/spec-kit-analyze-consistency.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,017 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 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.1 $0.00097 $0.04017
Opus 5 $0.00048 $0.02008
Sonnet 5 $0.00019 $0.00803
Haiku 4.5 $0.00010 $0.00402

Measured 12d ago against content hash babae169b461, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

spec-kit-analyze-consistency 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 12d 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.

spec-kit-analyze-consistency/SKILL.md · 311 lines

How it starts

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

Analyze Consistency — Cross-Artifact Verification Skill

Purpose

Answer one question honestly, with evidence: is it safe to move from tasks.md to spec-kit-execute-tasks? This skill cross-checks spec.md, plan.md, and tasks.md against each other — coverage, traceability, Safe Deferral consistency, and story-closure completeness — and reports findings. It is the fourth link in the spec-kit chain, and the only one that is purely read-only: it never edits spec.md, plan.md, tasks.md, or state.json. If something is wrong, the fix happens back in spec-kit-generate-spec, spec-kit-generate-plan, or spec-kit-generate-tasks — this skill only surfaces what needs fixing and how urgently.

User Input

$ARGUMENTS

Always consider the complete user message and any files or attachments available in the current conversation, even when $ARGUMENTS appears literally or is empty. The most common input is a reference to a feature directory; this skill checks whatever subset of spec.md/plan.md/ tasks.md actually exists there.

Core Principle

Every finding is a citation, not an impression. Every finding is classified as BLOCKING or ADVISORY — never left ambiguous about how urgent it is.

  • A finding without a concrete ID (an R-FR##, O-0#, T0##, file/line) is not a finding, it's a hunch — do not report one.
  • BLOCKING findings are the ones that mean spec-kit-execute-tasks would build on a gap that can break something (an unverified safeguard, an unsafe deferral, an incomplete story closure, a task with no traceable scope). ADVISORY findings are real but not urgent enough to halt on their own (an uncovered nice-to-have requirement, terminology drift, an operation without a task in a feature that intentionally stops short of full coverage this release).
  • This skill does not decide how to fix anything — that is the job of whichever upstream skill owns the artifact with the gap.

Non-Negotiable Rules

Read the full file on GitHub · 311 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. 12d ago First seen · 311 lines · 97 tokens per session scan A babae169b461

Subscribe to this mod's changes

spec-kit-analyze-consistency is a skill published in the GitHub repository ErikaAX08/erikas-skills (5 stars, last pushed 12d ago), licensed MIT. It adds 97 tokens to every session and 4,017 once invoked, about $0.0005 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.