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-clarify-intentgit 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-clarify-intent)<a href="https://agentmods.dev/skills/uniqbit-ag/mate-cli/mate-clarify-intent"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-clarify-intent/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-clarify-intent"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-clarify-intent.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.00053 | $0.00865 |
| Opus 5.5 | $0.00021 | $0.00346 |
| Sonnet 5.5 | $0.00011 | $0.00173 |
| Haiku 4.5 | $0.00005 | $0.00086 |
Grade A, and why
mate-clarify-intent 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mate Clarify Intent
The optional first stage of the Delivery Path. It runs before /mate-explore-change
and decides how much clarification a request needs: an interview when intent is
incomplete, grilling when intent is clear but a proposed direction needs testing, or
nothing at all for a small, fully specified change.
Read only the user's request and this conversation. Do not read or investigate the repository; questions that need repository evidence go to explore.
Step 1: Fill the slot table
Mark each slot stated, implied, or missing from the request and conversation:
| Slot | Question |
|---|---|
| Who | Who benefits or is affected? |
| Why | What problem or change makes this needed now? |
| Success | How will we know it worked? |
| Constraint | What limit binds the solution? |
implied Success counts as missing: a guessed success measure is the gap this stage
exists to close. Then note whether the request proposes a direction (an approach,
design, or solution shape): yes or no.
Step 2: Route
Apply the first rule that matches:
- Any slot
missing→ interview. - All slots filled and a direction is proposed → grill.
- All slots filled, no direction, and the change is minimal-eligible (one Area, low risk, no new dependency or data-model change) → skip.
- Otherwise → grill.
Step 3: Announce and accept an override
Show the slot table with each slot's mark, the direction answer, and the route with its rule in one line, for example:
Route: interview — Success is missing.
Reply `interview`, `grill`, or `skip` to switch; anything else continues.
A one-word reply interview, grill, or skip replaces the route without further
questions. Run exactly one mode.
Step 4: Run the routed mode
Run the mode by reading its instructions and following them, not by invoking a skill. Resolve the file relative to this skill's own directory:
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 · 96 lines · 53 tokens per session scan A 4ee680eb93c7
mate-clarify-intent is a skill published in the GitHub repository uniqbit-ag/mate-cli (12 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 865 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…