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 agentmods add skills/uniqbit-ag/mate-cli/mate-openspec-backfillnpx skills add uniqbit-ag/mate-cli --skill mate-openspec-backfillgit 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-openspec-backfill)<a href="https://agentmods.dev/skills/uniqbit-ag/mate-cli/mate-openspec-backfill"><img src="https://agentmods.dev/badge/skills/uniqbit-ag/mate-cli/mate-openspec-backfill.svg" alt="Measured on agentmods" 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 | $0.00052 | $0.01031 |
| Opus 5 | $0.00026 | $0.00515 |
| Sonnet 5 | $0.00010 | $0.00206 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
mate-openspec-backfill 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 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
Requirements state observable contracts, never implementation detail ("propagates the child exit code", not "uses spawnSync"). How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a spec for one feature that already exists in the working repository. The run ends with a standard ready-to-finish change — it never edits main specs and never finishes.
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. 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 (MODIFIED/ADDEDdeltas) 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 (with a follow-up fix change). Suspected bugs never silently become requirements.
[inferred]findings → confirm, demote to out-of-scope, or convert to a question the emitted proposal records as open.
-
Emit. Create the change and build its artifacts in dependency order:
openspec new change "backfill-spec-<capability>" openspec status --change "backfill-spec-<capability>" --json openspec instructions <artifact-id> --change "backfill-spec-<capability>" --json
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 First seen · 66 lines · 52 tokens per session scan A 8baa99df7d36
mate-openspec-backfill is a skill published in the GitHub repository uniqbit-ag/mate-cli (11 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 1,031 once invoked, about $0.0003 per session on Opus 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…