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-propose-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-propose-change)<a href="https://agentmods.dev/skills/uniqbit-ag/mate-cli/mate-propose-change"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-propose-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-propose-change"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-propose-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.00065 | $0.01243 |
| Opus 5.5 | $0.00026 | $0.00497 |
| Sonnet 5.5 | $0.00013 | $0.00249 |
| Haiku 4.5 | $0.00006 | $0.00124 |
Grade A, and why
mate-propose-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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mate Propose Change
The Propose change stage of the Delivery Path. It runs the OpenSpec propose workflow and adds the schema choice and one change per slice. Its revise mode reworks the plan of a change that already exists.
Step 0: Choose the mode
Use Revise mode when the named change already exists, or the user asks to revise, reconcile, or fold feedback or new decisions into a change's plan. Otherwise run the propose steps below.
Steps
-
Choose the schema. Use
mate-minimal(specs and tasks only) when every statement holds; otherwise usemate-v1(proposal, specs, design, tasks):- Intent and scope are clear, with nothing left to explore.
- The change stays within one Area.
- It is low risk: no new dependency, no data-model or public API change, and no security, performance, or migration concern.
Public API includes command names, flags, exit codes, JSON output fields, config keys, and exported package symbols.
State the result and the failing statement, if any, in one line. The user may override it.
-
One change per slice. Slicing test: a feature needs slicing when it spans several Areas, several independent behaviours, or more work than one review can hold (roughly more than 10 tasks or 400 changed lines). Several Areas that only work together stay one change with a scope per Area. When exploration agreed on several slices, propose one change per slice, each with its own name. When no slices were agreed, apply the slicing test before writing anything. If it passes, suggest slices in dependency order, naming their
dependsOnentries, and write no artifact until the user agrees to the slices or keeps one change. If the slice boundaries are unclear, suggest/mate-explore-changeinstead of guessing slices. Record a slice's dependency on an earlier change as adependsOnlist in the frontmatter of its first artifact, for exampledependsOn: [add-graph-model]; archive later warns while a dependency is still unarchived.
What ships with it
2 files 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 · 104 lines · 65 tokens per session scan A 4f9d08792a40
mate-propose-change is a skill published in the GitHub repository uniqbit-ag/mate-cli (12 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 1,243 once invoked, about $0.0003 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.