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/spec-merge-cleanup/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/spec-merge-cleanup)<a href="https://agentmods.dev/skills/sponge-b0b/polaris/spec-merge-cleanup"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/spec-merge-cleanup/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/spec-merge-cleanup"><img src="https://agentmods.dev/badge/skills/sponge-b0b/polaris/spec-merge-cleanup.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.00082 | $0.06805 |
| Opus 5 | $0.00041 | $0.03402 |
| Sonnet 5 | $0.00016 | $0.01361 |
| Haiku 4.5 | $0.00008 | $0.00681 |
Grade A, and why
spec-merge-cleanup 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 yesterday.
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 — 633 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Merge & Cleanup
Invoked by $review-spec only after its Exit Gate passes: zero Blocking findings, every Root Blocker satisfied, Owner-overridden, or Scope-retired, and no unresolved Candidate new root.
Execution splits depending on whether the Spec used spec-<spec_issue_number> and whether authoritative Spec completion has already occurred.
Session Independence
Assume no prior conversational or agent-session state.
Recover every correctness-critical input from the explicit invocation, repository, and durable tracker artifacts before acting. Prior-session summaries or remembered conclusions are routing context only and must not substitute for required durable evidence.
If required durable state cannot be recovered, report the missing artifact rather than infer or recreate it from memory.
Never assume an invocation is pre-merge merely because cleanup work remains. Detect whether the authoritative Spec completion transition has already occurred before applying any open-Spec or project-focus precondition.
Review Exit Authorization
Before closing or merging anything, and before resuming interrupted post-completion cleanup, recover the latest Spec Review Exit Receipt from the parent Spec issue. The parent Spec owns workspace metadata, Spec Verification Receipts, and the final review Exit Receipt. A conventional Spec Review issue is optional remediation history and must not be required for a clean first-pass review.
Read the parent Spec's complete durable comment history once:
REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner')
SPEC_NUMBER=<parent Spec issue number>
SPEC_COMMENT_PAGES=$(
gh api --paginate --slurp \
-H "X-GitHub-Api-Version: 2026-03-10" \
"repos/$REPO/issues/$SPEC_NUMBER/comments?per_page=100"
)
REVIEW_EXIT_RECEIPT_JSON=$(
printf '%s\n' "$SPEC_COMMENT_PAGES" \
| jq -c '
[.[][]
| select((.body // "") | contains("## Spec Review Exit Receipt"))
| {id, created_at, html_url, body}]
| sort_by(.created_at, .id)
| last // empty'
)
What ships with it
1 file 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.
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.
- yesterday Changed · +68 lines · +15 tokens per session 410f9a590d4c
- 11d ago First seen · 565 lines · 67 tokens per session scan A 773e22bfff2d
spec-merge-cleanup is a skill published in the GitHub repository sponge-b0b/Polaris (4 stars, last pushed today), licensed Apache-2.0. It adds 82 tokens to every session and 6,805 once invoked, about $0.0004 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.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
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…