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/resolve-ai-oss/resolve-ai-plugins/asknpx skills add resolve-ai-oss/resolve-ai-plugins --skill askgit clone --depth 1 https://github.com/resolve-ai-oss/resolve-ai-pluginsWrote 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/resolve-ai-oss/resolve-ai-plugins/ask)<a href="https://agentmods.dev/skills/resolve-ai-oss/resolve-ai-plugins/ask"><img src="https://agentmods.dev/badge/skills/resolve-ai-oss/resolve-ai-plugins/ask.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.00073 | $0.00607 |
| Opus 5 | $0.00036 | $0.00303 |
| Sonnet 5 | $0.00015 | $0.00121 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
ask 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ask Resolve
Use when the user wants Resolve to answer a question or do more investigation work.
Arguments
If $ARGUMENTS is non-empty, use it as the user's base message and proceed (enrich with conversation context as below, then call ask).
If $ARGUMENTS is empty (skill invoked without a clear question), ask the user once what they want to ask Resolve. Treat their next reply as the base message.
Composing the message
Before calling ask, enrich the user's base message with context from the current conversation that directly supports the specific question being asked.
Be ruthlessly selective. Do not dump every file you've read, every command you've run, or the conversation transcript. Include only what makes the question more answerable. If a piece of context isn't load-bearing for this specific message, leave it out.
Candidates to consider (include only those tied to the question):
- File paths the user opened or edited in the path of investigating this exact issue
- Error messages, log lines, or stack traces that name the symptom the user is asking about
- Git context (branch, recent commits, working changes) when the question is about a change being made
- URLs the user referenced that frame this question (Slack threads, dashboards, related canvases)
- A one-line framing of what the user is working on — only if the question doesn't stand on its own
Format the enriched message as the user's question first, then a brief ## Local context block with only the relevant items. Most asks need 1–3 lines of context, not a dump.
Picking scope
Default to whatever investigation/chat is currently in context:
- The user just engaged an investigation via
investigate→ scope the ask to it. - A chat is already in flight under that investigation → continue it.
- The user switches to a different investigation mid-conversation → start fresh there.
- No active context → standalone Resolve chat.
After asking
Call ask with the selected scope and enriched message, then surface the returned URL.
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 · 54 lines · 73 tokens per session scan A a4de08b93f5d
ask 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 73 tokens to every session and 607 once invoked, about $0.0004 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.
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…
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…
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…
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…