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 skills add resolve-ai-oss/resolve-ai-plugins --skill demogit 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/demo)<a href="https://agentmods.dev/skills/resolve-ai-oss/resolve-ai-plugins/demo"><img src="https://agentmods.dev/badge/skills/resolve-ai-oss/resolve-ai-plugins/demo.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.1 | $0.00105 | $0.02593 |
| Opus 5 | $0.00053 | $0.01296 |
| Sonnet 5 | $0.00021 | $0.00519 |
| Haiku 4.5 | $0.00011 | $0.00259 |
Grade A, and why
demo 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 8d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Demo Resolve
A guided, checkpointed walkthrough of Resolve using your connected org's live data. You drive each step at your own pace. The arc escalates:
surface → resume a chat → many in parallel → drill a real RCA (evidence + live thread) → turn the findings into a code-fix PR → investigate from scratch.
Every beat stands alone — stop anywhere and it's still a complete demo.
This skill orchestrates with direct tool calls and its own narration. For the streaming beats it follows the stream_command streaming already documented in the ask and investigate skills rather than restating the host-specific mechanics here.
Arguments
If $ARGUMENTS carries an emphasis (e.g. "focus on logs", "keep it short"), bias curation and beat selection toward it. Otherwise run the default arc. Treat a bare start as "begin the tour".
Two run modes
Establish the mode at the start and honor it for every command, every beat:
- Auto (default — today's behavior): you run each command via the tools, pausing at checkpoints for the user's "go" or to let them pick an option.
- Manual (hand-me-the-commands): you do not execute the beat's action. Compose the full command with its args/message filled in and present it for the user to type themselves, then stop and wait for them to run it before moving on. You may still run read-only setup (e.g.
overview) so the commands you hand over carry real IDs/values, but every action command (ask,investigate,steer,apply-fix) is theirs to enter. Because they're invoking the real skills, those skills' own run/format behavior (streaming, citations, canvas URLs) applies as-is.
Select via $ARGUMENTS (auto / manual); if unset, ask once at pre-flight.
Two registers in your output
- Tour narration (plain prose): the lines you walk the user through — clean, jargon-light, short.
- Control cue (prefix
▶): meta prompts to the user, not part of the narration. End every beat with a cue that previews exactly what the next step will do, e.g.▶ Next: open a real RCA and pull the raw telemetry behind its top theory. Say "go", pick from the menu, or tell me what to show. - Command tag (prefix
▷): name the slash command for each beat's capability. In auto mode it's just the label, so the user learns it —▷ Run it yourself: /resolve-ai:overview. In manual mode it's the full runnable command with composed args, and you stop and wait for the user to enter it — e.g.▷ Type this: /resolve-ai:ask Follow-up: of the error spikes in svc-analysis, which one is most worth acting on first?. Mapping (args from each skill's ownargument-hint): surface →/resolve-ai:overview(focused lists/resolve-ai:alerts,/resolve-ai:investigations,/resolve-ai:chats); resume / ask / thread / parallel →/resolve-ai:ask <message>; redirect a live investigation →/resolve-ai:steer <message>; drill or start an RCA →/resolve-ai:investigate <url-or-id | problem>; apply a fix →/resolve-ai:apply-fix.
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.
- 8d ago First seen · 128 lines · 105 tokens per session scan A 5e5716244ce1
demo is a skill published in the GitHub repository resolve-ai-oss/resolve-ai-plugins (4 stars, last pushed today), licensed Apache-2.0. It adds 105 tokens to every session and 2,593 once invoked, about $0.0005 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.