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/steering-patchnpx skills add microsoft/AutoSaddler --skill steering-patchgit 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.00029 | $0.01430 |
| Opus 5 | $0.00015 | $0.00715 |
| Sonnet 5 | $0.00006 | $0.00286 |
| Haiku 4.5 | $0.00003 | $0.00143 |
Grade A, and why
steering-patch 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 3d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Steering Patch
Overview
A steering patch refines the agent's behavior within the existing capabilities. It modifies how the agent uses existing tools — through prompt rules, tool description corrections, or hook reminders.
Key distinction from capability patches: A steering patch does not add
new tool methods, new parameters, or modify tool implementation code.
It only changes the text the agent reads (docstrings, prompts, hooks).
The outer loop selects which skill to use based on the current phase:
steering phase uses this skill, capability phase uses capability-patch.
When to Use
Based on the diagnosis results, generate a patch that resolves the identified root cause. Typical root causes addressable by steering patches:
| Root Cause Category | Signal | Example |
|---|---|---|
| Misleading description | Docstring doesn't match implementation | Agent uses correct tool but passes wrong parameter format |
| Missing description detail | Docstring lacks constraints or semantics | Agent has correct intent but doesn't know about a required field |
| Behavioral pattern failure | Multiple scenarios share the same mistake | Agent consistently forgets to check preconditions before acting |
| Missing runtime guidance | Agent needs just-in-time hints for specific tools | Agent misuses a tool because it doesn't recall a constraint at call time |
Workflow
Step 1: Consult History
Before writing any changes, check what has been tried before:
# Full patch history: diffs, reflections, lessons (good/bad patterns)
evo-dag show history
# Per-scenario history: prior root causes and attempted fixes
evo-dag show scenario <scenario_id>
- Build on proven strategies: Which steering patches generalized well to the dev set? What root-cause patterns did they resolve?
- Avoid known bad patterns: Which patches caused regressions or failed to generalize? Which rule phrasings were too weak or too aggressive?
- Do not re-attempt failed approaches: If a specific fix was already tried on this scenario and failed, try a different approach.
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.
- 3d ago First seen · 158 lines · 29 tokens per session scan A 1cf9a9ef54e3
steering-patch is a skill published in the GitHub repository microsoft/AutoSaddler (165 stars, last pushed 8d ago), licensed MIT. It adds 29 tokens to every session and 1,430 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-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…