A completion check for software built from a written specification. It compares the implementation with the requirements, tests, design, and quality checks.

Use it after implementing a spec to run tests, check coverage, type checking, linting, security, accessibility, performance, and required documentation.

It helps find missing acceptance criteria, untested error cases, failed checks, and documentation gaps before calling the work finished.

How sourjya/kiro-rails configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to sourjya/kiro-rails. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/sourjya/kiro-rails/main/.claude/skills/spec-verify/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/sourjya/kiro-rails

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sourjya/kiro-rails/spec-verify/github.svg)](https://agentmods.dev/skills/sourjya/kiro-rails/spec-verify)

Your own site

<a href="https://agentmods.dev/skills/sourjya/kiro-rails/spec-verify"><img src="https://agentmods.dev/badge/skills/sourjya/kiro-rails/spec-verify/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sourjya/kiro-rails/spec-verify"><img src="https://agentmods.dev/badge/skills/sourjya/kiro-rails/spec-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 497 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.

Model	Per session	Once invoked
Fable 5.1	$0.00031	$0.00497
Opus 5	$0.00015	$0.00249
Sonnet 5	$0.00006	$0.00099
Haiku 4.5	$0.00003	$0.00050

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

Security

Grade A, and why

spec-verify 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 10d 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.

.claude/skills/spec-verify/SKILL.md · 75 lines

What it actually says

Spec Verify Workflow

Verify that a completed implementation satisfies its spec.

Steps

Read the spec - load requirements.md and design.md
Run verification checks against each requirement
Generate a verification report
Flag any gaps for remediation

Verification Checklist

For each requirement in requirements.md:

Functional Verification

Every acceptance criterion has a passing test
Edge cases identified in design.md are handled
Error paths are tested (not just happy path)

Non-Functional Verification

Performance requirements met (if specified)
Security requirements met (no secrets, proper auth, input validation)
Accessibility requirements met (if frontend)

Code Quality

Tests pass (npm test / pytest / equivalent)
Type checking passes (if applicable)
No lint errors
No hardcoded values that should be configurable

Documentation

Code comments explain WHY, not WHAT
API changes documented
ADR written if architectural decisions were made
Changelog entry added

Verification Report

After checking, append a verification section to the spec folder:

<!-- Append to tasks.md -->

## Verification Results

**Date:** YYYY-MM-DD
**Status:** ✅ PASSED | ⚠️ PARTIAL | ❌ FAILED

### Requirements Coverage
| Requirement | Status | Notes |
|-------------|--------|-------|
| REQ-1 | ✅ | All criteria met |
| REQ-2 | ⚠️ | Missing edge case test |

### Gaps Found
- Gap 1: ...
- Gap 2: ...

### Recommendation
Ready for archive / Needs remediation on: ...

Rules

Be strict - a requirement is only "met" if ALL its acceptance criteria pass
Check tests exist - don't just trust that code works; verify tests cover it
Flag scope creep - if implementation added things not in the spec, note it
Recommend next step - either spec-archive (if passed) or remediation tasks

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.

10d ago First seen · 75 lines · 31 tokens per session scan A d1d99c7eb6d7

Subscribe to this mod's changes

spec-verify is a skill published in the GitHub repository sourjya/kiro-rails (9 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 497 once invoked, about $0.0002 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.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

kiro-rails: Skill for Claude Code