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.
curl -O https://raw.githubusercontent.com/sponge-b0b/Polaris/main/.agents/skills/contract-ledger/SKILL.mdgit clone --depth 1 https://github.com/sponge-b0b/PolarisWrote 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.
[](https://agentmods.dev/skills/sponge-b0b/polaris/contract-ledger)<a href="https://agentmods.dev/skills/sponge-b0b/polaris/contract-ledger"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/contract-ledger/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.
<a href="https://agentmods.dev/skills/sponge-b0b/polaris/contract-ledger"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/contract-ledger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00021 | $0.01346 |
| Opus 5.5 | $0.00008 | $0.00538 |
| Sonnet 5.5 | $0.00004 | $0.00269 |
| Haiku 4.5 | $0.00002 | $0.00135 |
Grade A, and why
contract-ledger 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.
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.
How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contract Ledger
$contract-ledger is the sole writer for Canonical Contract Ledger (CCL) transactions:
contracts/ccl/transactions/
Schema and deterministic mechanics:
contracts/ccl/schema/ccl-v1.schema.json
scripts/ccl.py
scripts/ccl_ledger.py
The CCL records material semantics. It does not plan projects, write Specs, decompose tickets, implement code, or perform review.
Invariants
- accepted transaction files are append-only and immutable;
- semantic change creates a new full-snapshot revision;
retireis terminal in CCL v1;- typed assertions are semantic authority;
display/annotationsare non-authoritative and excluded from the proposal hash;- absence of an assertion never authorizes downstream semantic invention;
- one transaction may revise several coupled contracts atomically, but never more than one revision of the same contract;
- every assertion is addressed as
<contract-id>@<revision>#<assertion-id>.
Never edit, replace, rename, or delete an accepted transaction to change its meaning.
Modes
lookup
Read-only exact/latest contract or assertion lookup:
python -m scripts.ccl_ledger lookup \
contracts/ccl/transactions \
<contract-id> \
[--revision <n>] \
[--assertion <assertion-id>]
When an exact CCL address exists, consume it instead of reinterpreting source prose.
existing-authority
Register semantics already fixed completely by current durable governing/constraint authority.
No new semantic choice or human decision is legal here. Every proposed assertion must be entailed at exactly the proposed strength.
Illegal strengthening includes:
may→must;- examples → required/closed taxonomy;
- optional → required relationship/cardinality;
- general durability → invented required public field;
- open vocabulary → closed enum;
- unspecified dimension → chosen default.
If normalization requires any such choice, return CCL ADMISSION: UNSUPPORTED.
owner-decision
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.
- 7d ago Changed · -94 lines 157ef3fbf170
- 8d ago First seen · 297 lines · 21 tokens per session scan A 9443e2df9918
contract-ledger is a skill published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 1,346 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-10-17.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.