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/microsoft/autosaddler/patch-verificationnpx skills add microsoft/AutoSaddler --skill patch-verificationgit clone --depth 1 https://github.com/microsoft/AutoSaddlerWhat 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.00038 | $0.00974 |
| Opus 5 | $0.00019 | $0.00487 |
| Sonnet 5 | $0.00008 | $0.00195 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
patch-verification 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 2d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Patch Verification
Overview
A patch that crashes or introduces bugs at runtime is worse than no patch at all. Every patch must pass thorough verification before being committed.
Only fix what would actually crash or produce incorrect behavior — do NOT change the patch's intent.
When to Use
After applying ANY patch type (capability or steering).
Verification Procedure
Step 1: Review the Diff
git diff
- Does the diff match your intent? No unintended changes?
- Are there leftover debug statements, commented-out code, or TODOs?
- Are there any files modified that should not have been changed?
Step 2: Syntax and Import Check
For every modified Python file:
python3 -m py_compile <modified_file>
python3 -c "import <modified_module>"
- No
SyntaxError,IndentationError, orTabError - No
ImportErrororModuleNotFoundError - No
NameErrorfrom undefined variables or functions at module level
Step 3: Docstring Integrity
Docstrings are the agent's only interface to tools — errors here directly cause agent failures.
- No placeholder values (
[...],{...},<placeholder>) — these crash downstream parsers - All examples use concrete, valid values
- Parameter names in the docstring match the actual method signature
- Return value description matches what the implementation actually returns
- No stale documentation from copy-paste (e.g., wrong tool name, wrong parameter list from another method)
- No literal escape sequences (
\n,\t, etc.) used to represent multi-line examples or formatting inside docstrings — these produce actual control characters in the parsed string and can causeSyntaxErroror silently corrupt the docstring text. Use triple-quoted strings with real newlines instead
Step 4: Template String Safety
If the patch modifies any string that uses .format() or f-string
interpolation:
- Every
{placeholder}has a corresponding.format()argument - No extra or missing placeholders from copy-paste
- No unescaped curly braces in literal text (use
{{and}}to escape) - No cross-file contamination between template variables
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.
- 2d ago First seen · 126 lines · 38 tokens per session scan A 38518d33a4ba
patch-verification is a skill published in the GitHub repository microsoft/AutoSaddler (150 stars, last pushed 7d ago), licensed MIT. It adds 38 tokens to every session and 974 once invoked, about $0.0002 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-30.
Other skills, from other repositories
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…