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/verify-ticket-closure/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/verify-ticket-closure)<a href="https://agentmods.dev/skills/sponge-b0b/polaris/verify-ticket-closure"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/verify-ticket-closure/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/verify-ticket-closure"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/verify-ticket-closure.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.00043 | $0.04796 |
| Opus 5 | $0.00022 | $0.02398 |
| Sonnet 5 | $0.00009 | $0.00959 |
| Haiku 4.5 | $0.00004 | $0.00480 |
Grade A, and why
verify-ticket-closure 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 today.
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 — 447 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Ticket Closure
Independently certify or reject closure of one immutable ticket candidate.
This skill is the single semantic closure authority for both ordinary Implementation Tickets and Spec Review remediation tickets.
The implementation actor may propose closure evidence, but it may not certify its own candidate.
Remediation extends the acceptance universe. It does not create a second verifier or a second verdict.
Certified Semantic Domain Finality
This section is authoritative and strengthens every later domain-construction/closure rule in this file.
When PASS depends on closing a material finite/discoverable semantic domain, the fresh verifier is not only proving the candidate. It is also certifying the membership interpretation used to define that domain.
For every such domain, preserve one compact Certified Closure Domain record in the verifier PASS returned to $implement-ticket:
Certified Closure Domain: <stable ND/domain ID>
Parent claim/root: <AC-n / RB-n when applicable>
Authority identity: <exact durable source identities/hashes when available>
Membership predicate: <what makes a candidate a member>
Dimensions / authoritative source sets: <explicit sets or bounded sources>
Closure criterion: <expected count | independently checkable open-world criterion>
Expected/generated/inspected/dispositioned: <counts when finite>
Material out-of-domain boundary observations: <concise list/families when needed>
Finality: frozen-under-unchanged-authority
A domain record is required when domain construction materially contributes to semantic PASS. Do not hide the final membership interpretation only inside narrative evidence.
Before PASS require:
Material closure domains required: <n>
Certified closure-domain records: <n>
Missing domain records: 0
Unresolved domain identities: 0
The verifier must derive each record from the same durable authority/membership predicate already required below. The record does not broaden that authority.
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.
- today Changed · +6 lines b65df92213cb
- 4d ago Changed · +153 lines 56764d67cade
- 6d ago First seen · 288 lines · 43 tokens per session scan A f755c054198e
verify-ticket-closure is a skill published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed today), licensed Apache-2.0. It adds 43 tokens to every session and 4,796 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-09-04.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
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"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…