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-show-megit 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-show-me)<a href="https://agentmods.dev/skills/uniqbit-ag/mate-cli/mate-show-me"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-show-me/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-show-me"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-show-me.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.00068 | $0.03226 |
| Opus 5.5 | $0.00027 | $0.01290 |
| Sonnet 5.5 | $0.00014 | $0.00645 |
| Haiku 4.5 | $0.00007 | $0.00323 |
Grade A, and why
mate-show-me 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mate Show Me
Explain the current topic visually in a browser-rendered Mate report. Skip the preamble, keep prose brief, and pick the smallest report view that makes the key point clear.
Subject
- With no argument, review the applied change when the user asks what a change did, or when the conversation is about work in the Working Repository and
git diffthere is not empty; otherwise explain the current topic. When both readings fit, review the change. - With an argument naming a spec capability (
$ARGUMENTS, for exampleacme-capability), explain that capability instead: read its canonical spec underopenspec/specs/in the Companion Repository and report its purpose, its requirements, and the flow or structure they establish. Name the capability in the reportmetadata, include adiagramsection, and omit thediffsection. - When the named capability has no canonical spec, say so, suggest close capability names from
openspec/specs/, and write nothing: no report, no file.
Mate Workflow
- Explanation only. Never write or edit source code, tests, documentation, OpenSpec artifacts, context files, or ADRs. The only file this skill produces is the report document handed to
mate report --input; the CLI hosts or opens the rendered report. - Draw from the repositories, not from memory. Every diagram and every diff line comes from the inspected repository state, never from recollection of the conversation. Use the available code-graph tools before broad source scans.
- Code lives in the Working Repository; the Companion Repository holds only artifacts. Run
git diffin the Working Repository. - Never put an absolute local path, home directory, username, machine name, temporary report path, Companion Repository path, or raw path-valued environment variable in the report. Use repository-relative paths or neutral labels such as
Working RepositoryandCompanion Repository. - Never commit, push, or create a pull request.
Browser Report Required
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.
- 5d ago Changed · +58 lines 857241dffc44
- 17d ago Changed 7bda10cae936
- 21d ago Changed · +6 lines · +12 tokens per session 42bdac3dd7f2
- 23d ago Changed · +3 lines 7ccd84f967cf
- 1mo ago First seen · 140 lines · 56 tokens per session scan A 3ecf5d44eb45
mate-show-me is a skill published in the GitHub repository uniqbit-ag/mate-cli (12 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 3,226 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-09-12.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…