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.
npx skills add uniqbit-ag/mate-cli --skill mate-archive-changegit clone --depth 1 https://github.com/uniqbit-ag/mate-cliWrote 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/uniqbit-ag/mate-cli/mate-archive-change)<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.
<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>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.00054 | $0.00622 |
| Opus 5.5 | $0.00022 | $0.00249 |
| Sonnet 5.5 | $0.00011 | $0.00124 |
| Haiku 4.5 | $0.00005 | $0.00062 |
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.
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
-
Archive.
mate artifact archive "<change-name>" --jsonRun 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 runsopenspec archiveitself. Do not runopenspec archiveseparately. -
Answer a missing branch. When the result's
statusisneeds-branch, nothing was archived. Ask the user which branch delivers the change, suggestingsuggestedBranchwhen 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.
-
Report. Relay every entry of
warningsfirst: 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 archivepathand the delivery: each branch with its merge result and source (forgeoruser) and PR link, or the not-applicable reason. An open or unknown merge is information, not a failure. -
Hand off. Name
/mate-publish-artifactas 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.
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 First seen · 60 lines · 54 tokens per session scan A 626f916c515d
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.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
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.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.