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 Oriolshhh/runware-image-mcp --skill debuggit clone --depth 1 https://github.com/Oriolshhh/runware-image-mcpWrote 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/oriolshhh/runware-image-mcp/debug)<a href="https://agentmods.dev/skills/oriolshhh/runware-image-mcp/debug"><img src="https://agentmods.dev/badge/skills/oriolshhh/runware-image-mcp/debug/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/oriolshhh/runware-image-mcp/debug"><img src="https://agentmods.dev/badge/skills/oriolshhh/runware-image-mcp/debug.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.00019 | $0.00708 |
| Opus 5.5 | $0.00008 | $0.00283 |
| Sonnet 5.5 | $0.00004 | $0.00142 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
debug 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/debug — Diagnose and fix a failure
Purpose
Find and correct the causal defect rather than patching symptoms or cycling through speculative edits.
Invocation
/debug <symptom, failing command, error, or reproduction>
Accepted input
Observed and expected behavior, logs/errors, reproduction steps or command, environment, suspected area, and recent changes when known.
Prerequisites
A HarnessKit workspace and permission to run the relevant local reproduction and
tests. Read the configured maximum with harnesskit loop list.
Procedure
Follow .agent/loops/debug-loop.yml, counting one full
reproduce→investigate→hypothesize→experiment/fix→verify pass as one iteration:
- Reuse a supplied context capsule; otherwise apply
context-discoveryonce and construct a task-specific capsule before broad exploration. - Record expected/observed behavior, environment, and exact reproduction.
- Reproduce without editing. Reduce the case and trace the narrowest failing path.
- Maintain an evidence ledger and rank falsifiable hypotheses.
Apply
model-routing: a stable, localized reproduction may use standard/medium; retain heavy/high for ambiguous, cross-boundary, concurrent, security-sensitive, or repeatedly falsified investigations. - Run the highest-information controlled experiment, changing one variable.
- If evidence identifies the root cause, add a regression test and apply the smallest safe fix. Otherwise begin the next iteration with the new evidence.
- Verify the original reproduction, regression, adjacent behavior, and gates.
- Stop immediately on verified success. At
max_iterations, stop and return the ledger, remaining hypotheses, and next discriminating experiment.
Approval points
- Ask before destructive, networked, credentialed, production, expensive, or externally visible diagnostics.
- Requirement or public-contract changes return to
/specfor approval.
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 · 73 lines · 19 tokens per session scan A 48484f5ecacc
debug is a skill published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 708 once invoked, about $0.0001 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…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
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.