A command for sending a new finding, hypothesis, or direction to an active Resolve investigation.

It helps report evidence such as file paths, errors, timings, branch details, or related URLs to redirect an investigation.

It lets local observations become part of the central investigation instead of remaining isolated in a chat or code session.

steer — Skill for Claude Code by resolve-ai-oss: A command for sending a new finding, hypothesis, or…

Install

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.

agentmods

npx agentmods add skills/resolve-ai-oss/resolve-ai-plugins/steer

Any agent

npx skills add resolve-ai-oss/resolve-ai-plugins --skill steer

Clone the repo

git clone --depth 1 https://github.com/resolve-ai-oss/resolve-ai-plugins

Made for: Claude Code.

Or install resolve-ai, the plugin that ships this one along with the rest of its 13 skills, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/resolve-ai-oss/resolve-ai-plugins/steer.svg)](https://agentmods.dev/skills/resolve-ai-oss/resolve-ai-plugins/steer)

Your own site

<a href="https://agentmods.dev/skills/resolve-ai-oss/resolve-ai-plugins/steer"><img src="https://agentmods.dev/badge/skills/resolve-ai-oss/resolve-ai-plugins/steer.svg" alt="Measured on agentmods" height="20"></a>

Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 507 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00067	$0.00507
Opus 5	$0.00034	$0.00253
Sonnet 5	$0.00013	$0.00101
Haiku 4.5	$0.00007	$0.00051

Measured 5d ago against content hash 987120629ceb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

steer 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 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.

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.

plugins/claude/resolve-ai/skills/steer/SKILL.md · 48 lines

What it actually says

Steer Investigation

Send a directive to an active investigation. This is the canonical channel for promoting local observations into Resolve's investigation flow.

Arguments

If $ARGUMENTS is non-empty, use it as the base of the steer message. Enrich with conversation context as below before calling steer_investigation.

If $ARGUMENTS is empty, ask the user once what they want to steer Resolve with. Treat their next reply as the base.

Enriching with conversation context

Before calling the tool, expand the base message with conversation signals that directly support the finding being promoted. Be ruthlessly selective:

Specific file paths or code snippets that demonstrate the finding
Error messages or log lines from this conversation that back up the observation
Git context (branch, commit) if the finding is tied to a local change
URLs the user referenced that informed the finding

If a piece of context doesn't strengthen the steer, leave it out.

Composing the message

A good steer message is:

Specific. "Latency spike correlates with the 14:52 deploy of the affected service" beats "I think it's the deploy."
Anchored. Reference times, services, files, or theory IDs from get_investigation when relevant.
Actionable. Either an observation Resolve should integrate, or a directive for the agent teams ("focus on the connection pool theory").
Markdown. Bullets, file paths, code references — anything the human side of an investigation would benefit from.

After steering

Effects surface via:

The activity timeline — re-read via read_file on the timeline path from get_investigation.
Updated theories on next get_investigation.
Live, if the user wants to watch the effect land: follow any returned stream with the host's long-running command mechanism.

Changes

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 · 48 lines · 67 tokens per session scan A 987120629ceb

Subscribe to this mod's changes

steer is a skill published in the GitHub repository resolve-ai-oss/resolve-ai-plugins (4 stars, last pushed 11d ago), licensed Apache-2.0. It adds 67 tokens to every session and 507 once invoked, about $0.0003 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.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

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…

openai/codex · 113 tokens