A specification-wide verification workflow that checks a completed specification's implementation against its fixed acceptance contract. It records proof for each applicable requirement and creates a receipt for the exact final commit.

Running deterministic verification gates, repairing failures owned by the specification, proving each applicable requirement, and recording the final verification receipt.

It catches integration failures that may be missed when individual parts are checked separately. Its evidence-based gates also distinguish required checks from irrelevant ones.

How sponge-b0b/Polaris configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to sponge-b0b/Polaris. 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/sponge-b0b/Polaris/main/.agents/skills/verify-spec/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/sponge-b0b/Polaris

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sponge-b0b/polaris/verify-spec/github.svg)](https://agentmods.dev/skills/sponge-b0b/polaris/verify-spec)

Your own site

<a href="https://agentmods.dev/skills/sponge-b0b/polaris/verify-spec"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/verify-spec/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/sponge-b0b/polaris/verify-spec"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/verify-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 8,064 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00037	$0.08064
Opus 5	$0.00018	$0.04032
Sonnet 5	$0.00007	$0.01613
Haiku 4.5	$0.00004	$0.00806

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

Security

Grade A, and why

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

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/verify_spec_artifacts.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.agents/skills/verify-spec/SKILL.md · 727 lines

How it starts

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

Global Specification Integration & Verification

Verify a completed Spec as one integrated acceptance universe and record a passing receipt only after a fresh independent $verify-spec-closure certifier proves the exact stable HEAD.

This SKILL.md is the single authoritative procedure for $verify-spec. The preserved integration/gate/repair/finalization procedure later in this file remains normative except where the hardening sections immediately below explicitly supersede older wording.

Authorized Verification Scope and Repair Attribution

This section is authoritative and supersedes preserved wording that treats Git-derived Spec-owned/Mixed labels as semantic ownership, uses repository-wide Ruff/Mypy scope by default, or allows a gate failure to authorize repair merely because the affected file changed on the Spec branch.

$spec-contract now supplies change provenance, not semantic lifecycle ownership. Preserve the complete branch-local, mixed-provenance, inherited-only, and unchanged/named candidate universe it returns.

Before executing any scope-sensitive gate, build one working Verification Scope Manifest from that provenance plus exact Spec obligations and directly affected consumer/contract surfaces:

Gate: <gate identity>
Candidate: <repository/tracker/consumer surface>
Provenance: <branch-local | mixed-provenance | inherited-only | unchanged/named>
Scope disposition: <target | excluded | unresolved>
Authority/reason: <exact contract/impact reason>

Rules:

every candidate relevant to a gate receives exactly one disposition; omission is not exclusion;
target means the gate must include the candidate;
excluded requires durable authority or independently checkable evidence that the candidate cannot affect the active Spec verification claim; path/category/branch locality alone is insufficient;
unresolved blocks PASS;
contract-impact discovery may add unchanged consumers when they can observe a Spec-relevant transition;
do not invent repository-wide scope merely because a tool accepts .;
repository-wide scope is legal only when an exact active Spec obligation/contract transition is itself repository-wide or another authoritative gate contract explicitly requires whole-repository execution;
when repository-wide scope is not authorized, later preserved examples using ruff ... . or mypy . are superseded.

Read the full file on GitHub · 727 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2d ago Changed · +165 lines · +7 tokens per session 09f80c5f2205
4d ago Changed · -56 lines · -14 tokens per session e9acacca6a9e
8d ago First seen · 618 lines · 44 tokens per session scan A 834a07902199

Subscribe to this mod's changes

verify-spec is a skill published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 8,064 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

Polaris: Skill for Claude Code