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 debug-integrationgit 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/debug-integration)<a href="https://agentmods.dev/skills/resolve-ai-oss/resolve-ai-plugins/debug-integration"><img src="https://agentmods.dev/badge/skills/resolve-ai-oss/resolve-ai-plugins/debug-integration/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/resolve-ai-oss/resolve-ai-plugins/debug-integration"><img src="https://agentmods.dev/badge/skills/resolve-ai-oss/resolve-ai-plugins/debug-integration.svg" alt="Reviewed on agentmods" width="80" 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.00099 | $0.00730 |
| Opus 5.5 | $0.00040 | $0.00292 |
| Sonnet 5.5 | $0.00020 | $0.00146 |
| Haiku 4.5 | $0.00010 | $0.00073 |
Grade A, and why
debug-integration 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 1mo 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug a Resolve integration
Use when the user wants Resolve to diagnose or explain one of their integrations. The Resolve agent has internal tools to list integrations, load schema + redacted values + last health check + satellite scope, and (for satellite-backed integrations) read pod logs scoped to the right namespace.
This skill is read-only. To create or mutate integrations, see resolve-ai-admin:create-integration. To edit satellite Helm values, see resolve-ai-admin:satellite-configs.
Arguments
If $ARGUMENTS is non-empty, treat it as the user's question and proceed.
If $ARGUMENTS is empty (skill invoked without a clear question), ask the user once what's wrong with which integration. Treat their next reply as the base message.
Composing the ask
Compose one message for resolve-ai:ask. The agent will discover the target integration internally (list_integrations → get_integration_details) and invoke its own integration-debug skill to apply the diagnostic discipline (kubectl scoping rules, structured output formats).
You don't need to specify the integration instance id — describing the integration by name and symptom is sufficient. The agent will resolve which instance the user means.
Enrich the base message with conversation context that directly supports debugging this integration. Be ruthlessly selective:
- Error messages, log lines, or stack traces the user has shown that name the symptom
- Recent changes (deploys, config edits) that might be tied to the failure
- Health-check output the user pasted, if any
Format the enriched message as the user's question first, then a brief ## Local context block with only the relevant items. Hand that single composed message to resolve-ai:ask; it owns sending, scoping, streaming, and canvas URL handling.
After asking
Once resolve-ai:ask has produced its streamed or settled answer, expect a Mode A 4-block diagnosis (starts with **What's failing:** and includes Evidence / Likely cause / Suggested next step) when the user asked about a failure, or a Mode B field tour when they asked about config fields. Surface this verbatim — don't paraphrase the structured blocks.
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.
- 1mo ago First seen · 49 lines · 99 tokens per session scan A 48ae7ac2c5d2
debug-integration is a skill published in the GitHub repository resolve-ai-oss/resolve-ai-plugins (4 stars, last pushed 2d ago), licensed Apache-2.0. It adds 99 tokens to every session and 730 once invoked, about $0.0004 per session on Opus 5.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.
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…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.