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-publish-artifactgit 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-publish-artifact)<a href="https://agentmods.dev/skills/uniqbit-ag/mate-cli/mate-publish-artifact"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-publish-artifact/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-publish-artifact"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-publish-artifact.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.00061 | $0.05614 |
| Opus 5.5 | $0.00024 | $0.02246 |
| Sonnet 5.5 | $0.00012 | $0.01123 |
| Haiku 4.5 | $0.00006 | $0.00561 |
Grade A, and why
mate-publish-artifact 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish archived work deliberately: discover what is pending, let the user select it, restate what that selection ships, then run the deterministic publish pipeline for each selection.
Workflow
Archiving a change is a local OpenSpec operation and never publishes anything. Publication is this skill: an explicit selection followed by mate artifact publish calls. That CLI owns capability sync, the scoped commit, remote synchronization, the dated tag, the push, and conflict handoff. For a change it publishes work that is already archived and refuses anything that is not archived yet. Archiving is a precondition owned by mate-archive-change, which may run before the merge. This skill discovers, settles each archive's delivery, selects, sequences, and reports.
Published canonical specs describe the default branch, so an archive is publishable only when every delivery branch in its delivery.yaml is merged, or it is marked not applicable. Anything else stays visible but is waiting for merge and cannot be selected. An archive without a delivery.yaml is a legacy archive (made before delivery records, or past mate artifact archive); it is selectable, and mate artifact publish publishes it with a warning that its merge was not checked. An archive sharing a canonical spec with a held-back pending archive is refused by mate artifact publish too, since its commit would carry that archive's unmerged requirements.
Two things publish, and they are separate units:
- An archived change — its archive directory plus the canonical specs its delta specs name, under the tag
openspec/<date>-<name>. - Drifted canonical specs — uncommitted specs under
openspec/specs/that no pending change accounts for, published together under their own new tagopenspec/specs/<date>-<specs>, which names both the day it ran and the specs it ships.
A drifted spec is published in its own right. It is never shipped by republishing an old archive that once touched it, so publishing one never reuses another change's anchor, never files today's edit under an old change's commit message, and never leaves an existing tag standing in front of new content.
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 · 254 lines · 61 tokens per session scan A 1ae99a0aaa5f
mate-publish-artifact is a skill published in the GitHub repository uniqbit-ag/mate-cli (12 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 5,614 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
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.