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/rosenfan/matrix/matrix-verifynpx skills add Rosenfan/Matrix --skill matrix-verifygit clone --depth 1 https://github.com/Rosenfan/MatrixWrote 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/rosenfan/matrix/matrix-verify)<a href="https://agentmods.dev/skills/rosenfan/matrix/matrix-verify"><img src="https://agentmods.dev/badge/skills/rosenfan/matrix/matrix-verify.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.00026 | $0.01068 |
| Opus 5 | $0.00013 | $0.00534 |
| Sonnet 5 | $0.00005 | $0.00214 |
| Haiku 4.5 | $0.00003 | $0.00107 |
Grade A, and why
matrix-verify 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Matrix Verify
Run the approved Contract's acceptance commands and record their output summaries under ## Test evidence in artifacts/verification.md.
Write verification prose in artifact_language from inspect while preserving the required English evidence headings.
Input Sources
This phase can receive implementation from two sources:
- Direct Codex implementation — from
$matrix-buildphase - Claude Code implementation — from
$matrix-claudesidecar
Regardless of source, the verification process is the same: check that implementation evidence meets the plan's requirements.
Prerequisites
Before starting verification, ensure:
-
artifacts/verification.mdexists -
## Build evidencesection is present and substantive - All commands from the plan's
## Validationsection have been run - Test results are recorded
If these are missing (e.g., Claude Code didn't produce complete evidence), return to $matrix-build or ask Claude Code to补充.
Orchestration
Run node <matrix-skill-directory>/scripts/matrix-runtime.mjs inspect and read the frozen mode.
- Prim: Matrix performs the Standards and Spec review itself.
- Arch: invoke
code-reviewto produce both review axes; announce the invocation and reason.
Review findings are inputs to Matrix Verify; a companion cannot decide the phase outcome, broaden approved architecture, transition, or archive. Do not invoke post-review architecture wrappers. A correctly installed review capability gets at most one same-capability Matrix fallback; installation-integrity failure stops verification.
Under ## Review evidence, preserve two substantive subsections named ### Standards and ### Spec. Arch must then ask the project Runtime to bind those results to the current revision:
node <matrix-skill-directory>/scripts/matrix-runtime.mjs review --source code-review --fixed-point <ref> --standards <passed|failed> --spec <passed|failed>
If code-review cannot run because the Git baseline is unavailable, the committed HEAD diff is empty, staged/unstaged/untracked candidate files exist, or the capability actually fails, document that limitation and use the single bounded fallback for this revision:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +16 lines 220442f56d6b
- 4d ago First seen · 74 lines · 26 tokens per session scan A a603c3da3b45
matrix-verify is a skill published in the GitHub repository Rosenfan/Matrix (5 stars, last pushed 3d ago), licensed MIT. It adds 26 tokens to every session and 1,068 once invoked, about $0.0001 per session on Opus 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-08-31.
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…