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 commands/oriolshhh/runware-image-mcp/debuggit clone --depth 1 https://github.com/Oriolshhh/runware-image-mcpWhat 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.00050 | $0.00678 |
| Opus 5 | $0.00025 | $0.00339 |
| Sonnet 5 | $0.00010 | $0.00136 |
| Haiku 4.5 | $0.00005 | $0.00068 |
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 yesterday.
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 — 74 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.
Expected output
A verified minimal fix with regression coverage and exact commands/results, or a bounded blocked report containing iteration count, evidence, rejected/remaining hypotheses, and next experiment.
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.
- yesterday First seen · 74 lines · 50 tokens per session scan A f4b03a76d07b
debug is a command published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 678 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.