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-backfill-specgit 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-backfill-spec)<a href="https://agentmods.dev/skills/uniqbit-ag/mate-cli/mate-backfill-spec"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-backfill-spec/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-backfill-spec"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-backfill-spec.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.00052 | $0.01503 |
| Opus 5.5 | $0.00021 | $0.00601 |
| Sonnet 5.5 | $0.00010 | $0.00301 |
| Haiku 4.5 | $0.00005 | $0.00150 |
Grade A, and why
mate-backfill-spec scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
In both cases every requirement you write carries each per-requirement marker the schema requires (for example an `**Area:**` marker whose value appears in the spec's frontmatter). Requirements state observable contracts How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mate OpenSpec Backfill
Specify one feature that already exists in the working repository. A backfill records behavior that already shipped, so the run writes the canonical spec openspec/specs/<capability>/spec.md directly and leaves it uncommitted. It never creates a change and never publishes; publication happens afterwards through mate-publish-artifact.
Scope rules
- One named feature per run. Refuse Area-wide or repository-wide sweeps; ask the user to name a single feature and run the skill once per feature.
- Interactive by design. Every ambiguity and every suspected bug becomes a user question, and nothing is written before the user approves the review table. Do not run this skill unattended.
Steps
-
Scope. Map the named feature to code: entry points, callees, tests. Use whatever exploration tooling this project has enabled (code-graph or index tools when present, otherwise search and targeted reading) — assume no specific capability is installed. Then check
openspec/specs/for an existing capability covering this domain — prefer extending it in place over minting a new capability id. -
Sweep. Extract candidate behaviors and tag each finding:
[test-backed]— an existing test verifies it (strongest; scenarios translate almost directly from tests)[code-only]— observable in code but untested[inferred]— assumed intent without direct evidence
Every candidate requirement needs at least one citation: a test name or
file:line. Docs and comments corroborate but never stand alone.[inferred]findings are not requirements — they become questions for step 3. -
Ask. Batch the open questions to the user:
- Behavior that looks unintended → the user rules spec the actual behavior or spec the intent (and the user may open a separate fix change). Suspected bugs never silently become requirements.
[inferred]findings → confirm, demote to out-of-scope, or drop.
-
Review. Before writing any file, present every drafted requirement in one table and wait for the user's approval:
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 · 84 lines · 52 tokens per session scan A 800770efbe7c
mate-backfill-spec is a skill published in the GitHub repository uniqbit-ag/mate-cli (12 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 1,503 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). 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…