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-apply-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-apply-change)<a href="https://agentmods.dev/skills/uniqbit-ag/mate-cli/mate-apply-change"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-apply-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-apply-change"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-apply-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.00051 | $0.00840 |
| Opus 5.5 | $0.00020 | $0.00336 |
| Sonnet 5.5 | $0.00010 | $0.00168 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
mate-apply-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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mate Apply Change
The Apply change stage of the Delivery Path. Before any code changes, it records the Working Repository branch the change is delivered through, so archive and publication later know which merge to wait for. Then it runs the OpenSpec apply workflow.
Step 1: Read the branch and the record
In the Working Repository, read local Git state only:
git symbolic-ref --quiet --short HEAD # current branch; fails when detached
git symbolic-ref --quiet --short refs/remotes/origin/HEAD # default branch
Read the change's existing record without changing it:
mate artifact link "<change-name>" --json
Step 2: Settle the delivery branch
A branch is protected when it is the default branch or matches a configured
protected pattern; mate artifact link refuses a
protected branch unless it is recorded as a direct delivery.
- A branch is already recorded and it is the current branch → continue. When the current branch differs, warn, name both branches, and ask before implementing whether to switch to the recorded branch or record the current one.
- On
change/<change-name>→ record it without asking:mate artifact link "<change-name>" --branch "change/<change-name>" --json. - On another unprotected branch (a shared feature branch) → ask once whether this change is delivered through it, then record it on confirmation.
- Detached HEAD → ask for the branch name, then record it.
- On a protected branch → do not implement there by default. First name every
local commit that is not on the remote (
git log --oneline HEAD --not --remotes) and leave them where they are; never move, reset, or rebase them. Then offer:- Create
change/<change-name>(default):git switch -c change/<change-name>; uncommitted edits carry over. Record it. - Use an existing branch: switch to the branch the user names and record it.
- Work directly here — only when the user explicitly chooses it. Record it as a
direct delivery:
mate artifact link "<change-name>" --branch "<branch>" --direct --json.
- Create
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.
- today First seen · 77 lines · 51 tokens per session scan A 0596ebc5ea49
mate-apply-change is a skill published in the GitHub repository uniqbit-ag/mate-cli (12 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 840 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.