Polaris: Skill for Claude Code

.agents/skills/spec-contract/SKILL.md

spec-contract is a skill for Claude Code, Codex from sponge-b0b/Polaris. It costs 24 tokens per session (932 once invoked), scanned A, original, Apache-2.0.

An internal helper that lists the exact requirements a Spec must satisfy and identifies which changes belong to that Spec.

In plain words
What is it for?
Use it to build or validate the requirement record used when checking and reviewing a Spec.
Why use it?
It prevents verification and review tools from using different requirement lists or confusing older integration work with current work.

Skill for Claude CodeCodex

Written for Claude Code and Codex: disable-model-invocation in frontmatter, but also agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents); mentions Codex; $skill-name invocation.

This is sponge-b0b/Polaris's own configuration. It tells Claude Code and Codex how to work on Polaris itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Polaris configures →

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/spec-contract/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.

agentmods badge for spec-contract

README.md
[![agentmods](https://agentmods.dev/badge/skills/sponge-b0b/polaris/spec-contract/github.svg)](https://agentmods.dev/skills/sponge-b0b/polaris/spec-contract)
Your own site
<a href="https://agentmods.dev/skills/sponge-b0b/polaris/spec-contract"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/spec-contract/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-contract

Your own site · 80×15
<a href="https://agentmods.dev/skills/sponge-b0b/polaris/spec-contract"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/spec-contract.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 932 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00932
Opus 5.5 $0.00010 $0.00373
Sonnet 5.5 $0.00005 $0.00186
Haiku 4.5 $0.00002 $0.00093

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

Security

Grade A, and why

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

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/classify_ownership.py, scripts/extract_source_units.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/spec-contract/SKILL.md · 125 lines

How it starts

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

Spec Contract

$spec-contract is a deterministic helper. It does not decide what a Spec means.

The Spec's material semantics are already frozen by exact CCL addresses in its spec-contract-ccl:v1 manifest. This helper converts that projection plus explicitly identified private implementation, testing, and exclusion cells into one reproducible contract universe for ticketing, implementation, verification, and review.

Contract cells

A CCL-backed software Spec exposes only:

  • OBL-* — material semantic obligations from spec-contract-ccl:v1; semantic payload is the exact ordered CCL address set;
  • IMP-* — private/mechanical implementation obligations from stable-ID bullets in ## Implementation Decisions;
  • TEST-* — proof/test obligations from stable-ID bullets in ## Testing Decisions;
  • EXC-* — exclusions from stable-ID bullets in ## Out of Scope.

Narrative sections are human context and never create hidden cells. If material behavior is missing, route the Spec back to $to-specs / semantic authority instead of interpreting prose here.

Do not build Source Unit inventories, classify prose as normative/non-normative, invent NORM-*, or infer architecture obligations from ADR/wiki/code prose.

Deterministic builder

Use:

python -m scripts.ccl_spec check <spec-body-file> contracts/ccl/transactions
python -m scripts.spec_contract build <issue-json> <contract-output>
python -m scripts.spec_contract validate <issue-json> <expected-contract>
python -m scripts.spec_contract check-coverage <contract-json> <coverage-json>

The canonical result schema is:

{
  "schema": "polaris.spec-contract/v1",
  "spec_body_hash": "...",
  "spec_contract_hash": "...",
  "cells": [
    {
      "cell": "OBL-001",
      "kind": "material-contract",
      "cell_hash": "...",
      "ccl": ["contract@1#assertion"]
    }
  ]
}

There is no secondary source-unit, normative-classification, or compatibility projection. The cells array is the complete contract universe.

Read the full file on GitHub · 125 lines

Files

What ships with it

3 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.

  1. 7d ago Changed · -84 lines · -3 tokens per session cac87288b5df
  2. 8d ago Changed · +45 lines · +1 tokens per session 74a6379a353e
  3. 10d ago Changed · -489 lines 4b3bb8fddabd
  4. 25d ago Changed · +46 lines 364454a6b201
  5. 28d ago Changed · +22 lines febba0a5ead0
  6. 1mo ago Changed · -9 lines 359d518b64c2
  7. 1mo ago Changed · -28 lines 0a355ca18e9b
  8. 1mo ago Changed · +8 lines 2bdf53d24b6d
  9. 1mo ago Changed · +68 lines a994d71baa06
  10. 1mo ago First seen · 546 lines · 26 tokens per session scan A 61f12f00da6f

Subscribe to this mod's changes

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

Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens