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-grillinggit 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-grilling)<a href="https://agentmods.dev/skills/uniqbit-ag/mate-cli/mate-grilling"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-grilling/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-grilling"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-grilling.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.00042 | $0.00491 |
| Opus 5.5 | $0.00017 | $0.00196 |
| Sonnet 5.5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
mate-grilling 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 22d ago.
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.
What it actually says
Mate Grilling
Stress-test the current plan or idea as a design tree. This is a conversation, not an implementation or documentation session: do not create or modify code, context files, ADRs, OpenSpec artifacts, or other files.
Rounds
Use this shape for each round:
Q1 - <question title>: <question body, including choices when useful>
Recommended: <your recommended answer and its trade-off>
- State the current design hypothesis and its intended outcome.
- Expand the unresolved design tree: boundaries, actors, state, dependencies, failure paths, constraints, and acceptance evidence.
- Order the frontier by dependency. Ask every question on the current frontier in one round, and present a recommended answer with the trade-off behind it.
- Wait for explicit user answers. Never treat an unanswered recommendation as a decision.
- Record the accepted decision in the next hypothesis, close resolved nodes, and continue with the next unblocked frontier.
Finding facts is the agent's job, not the user's. Look up only the facts that block a design decision, using the available environment, tools, or a sub-agent, instead of asking the user for them. When a question would need mapping large parts of the repository, do not investigate it; record it as an assumption or an unresolved question.
End when the frontier is empty and the user confirms shared understanding. If the user names a blocker, stop and report the design as incomplete rather than presenting it as settled. Return the accepted decisions, unresolved questions, and assumptions to the invoking skill, which decides the next step.
Guardrails
- Ask in rounds, not as a long questionnaire.
- Keep alternatives visible until the user chooses one.
- Challenge contradictions and missing failure behavior directly.
- Do not invoke another skill.
- Do not write files or persist the conversation.
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.
- 22d ago Changed · +2 lines · +24 tokens per session f37ff4dd9b6d
- 23d ago Changed · +3 lines 168a259e69ae
- 1mo ago First seen · 50 lines · 18 tokens per session scan A 9fa3fb50cc73
mate-grilling is a skill published in the GitHub repository uniqbit-ag/mate-cli (12 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 491 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-09-09.
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…