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-explore-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-explore-change)<a href="https://agentmods.dev/skills/uniqbit-ag/mate-cli/mate-explore-change"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-explore-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-explore-change"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-explore-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.00058 | $0.00576 |
| Opus 5.5 | $0.00023 | $0.00230 |
| Sonnet 5.5 | $0.00012 | $0.00115 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
mate-explore-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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mate Explore Change
The Explore change stage of the Delivery Path. It runs the OpenSpec explore workflow and adds two things: the scope comes from the companion context map, and a feature too large for one change is suggested as several.
Steps
-
Follow the OpenSpec workflow. Read references/openspec-explore.md and follow it for the exploration itself. When a
PRE-EXPLORE HANDOFFblock is in this conversation, treat its Confirmed points as settled and start from its Unresolved questions and Assumptions. -
Resolve scope from the context map. Before reading code, identify the canonical Working Repository (
org/repositoryfrom its Git remote) and the repository-relative Area (the owning package root in a monorepo). Read the Companion Repository'sCONTEXT-MAP.md, then only the repository-scoped map for that Working Repository, and load only the contexts it maps to that Area. Use their vocabulary in the exploration. When the map has no entry for the Area, say so instead of borrowing another Area's context. -
Suggest slicing when the feature is large. 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 the explored direction passes the test, propose slices: one change per slice, each reviewable and archivable on its own, in dependency order. Name the dependencies between slices; they become
dependsOnentries when the changes are proposed. Several slices may share one delivery branch. Slicing is a suggestion; the user decides. -
Hand off. End by naming
/mate-propose-changeas the next step, once per agreed slice. Do not invoke it.
Boundary
Exploration writes no product code. Agent artifacts written while exploring go to the Companion Repository, never the Working Repository.
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 · 51 lines · 58 tokens per session scan A 9cd07f9ee90c
mate-explore-change is a skill published in the GitHub repository uniqbit-ag/mate-cli (12 stars, last pushed today), licensed MIT. It adds 58 tokens to every session and 576 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…