mate-archive-change

mate-archive-change is a skill for Claude Code from uniqbit-ag/mate-cli. It costs 54 tokens per session (622 once invoked), scanned A, original, MIT.

A workflow for archiving an implemented change in an OpenSpec project. It records delivery information, applies the change's specification updates locally, and reports merge status and warnings.

In plain words
What is it for?
Use it to archive or finalize a change after implementation, including cases where the delivery branch still needs to be identified.
Why use it?
It closes out a delivered change while keeping the canonical specifications up to date. Archiving is local and uncommitted, so it does not publish the change or wait for a merge.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to archive or finalize a change after implementation, including cases where the delivery branch still needs to be identified.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/uniqbit-ag/mate-cli/mate-archive-change
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add uniqbit-ag/mate-cli --skill mate-archive-change
Clone the repo
git clone --depth 1 https://github.com/uniqbit-ag/mate-cli

Made for: Claude Code.

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 mate-archive-change

README.md
[![agentmods](https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-archive-change/github.svg)](https://agentmods.dev/skills/uniqbit-ag/mate-cli/mate-archive-change)
Your own site
<a href="https://agentmods.dev/skills/uniqbit-ag/mate-cli/mate-archive-change"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-archive-change/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 mate-archive-change

Your own site · 80×15
<a href="https://agentmods.dev/skills/uniqbit-ag/mate-cli/mate-archive-change"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-archive-change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 622 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.
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.00054 $0.00622
Opus 5.5 $0.00022 $0.00249
Sonnet 5.5 $0.00011 $0.00124
Haiku 4.5 $0.00005 $0.00062

Measured today against content hash 626f916c515d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mate-archive-change 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.

packages/mate-core/src/templates/mate-skills/agents/mate-archive-change/SKILL.md · 60 lines

How it starts

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

Mate Archive Change

The Archive change stage of the Delivery Path. Archiving applies the change's delta specs to the local canonical specs, so a feature's later changes build on it. It is allowed before the delivery branch merges: publication, not archive, waits for the merge. Archiving is local and uncommitted; it publishes nothing.

Steps

  1. Archive.

    mate artifact archive "<change-name>" --json
    

    Run it from the companion or the linked Working Repository. It shows warnings, refreshes merge state from the forge when a token is available, writes the change's delivery.yaml, and runs openspec archive itself. Do not run openspec archive separately.

  2. Answer a missing branch. When the result's status is needs-branch, nothing was archived. Ask the user which branch delivers the change, suggesting suggestedBranch when it is set, and re-run with exactly one of:

    • --branch "<branch>" — a protected branch only with --direct, after the user explicitly confirms a direct delivery;
    • --not-applicable "<reason>" — for a specification-only change;
    • --skip-branch — when the user skips the question; publication will ask again.
  3. Report. Relay every entry of warnings first: another active change that modifies the same requirement, a declared dependency that is not archived yet, or planning artifacts its schema requires that are missing (incomplete-planning). Warnings never block. Then report the archive path and the delivery: each branch with its merge result and source (forge or user) and PR link, or the not-applicable reason. An open or unknown merge is information, not a failure.

  4. Hand off. Name /mate-publish-artifact as the next step and say that publication holds the archive back until its delivery branch is merged. Do not invoke it.

When status is failed, report the message (typically incomplete tasks or a validation error) and stop.

Read the full file on GitHub · 60 lines

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. today First seen · 60 lines · 54 tokens per session scan A 626f916c515d

Subscribe to this mod's changes

mate-archive-change is a skill published in the GitHub repository uniqbit-ag/mate-cli (12 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 622 once invoked, about $0.0002 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-30.