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 Master0fFate/forloop-mcp --skill repo-debugginggit clone --depth 1 https://github.com/Master0fFate/forloop-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/master0ffate/forloop-mcp/repo-debugging)<a href="https://agentmods.dev/skills/master0ffate/forloop-mcp/repo-debugging"><img src="https://agentmods.dev/badge/skills/master0ffate/forloop-mcp/repo-debugging/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/master0ffate/forloop-mcp/repo-debugging"><img src="https://agentmods.dev/badge/skills/master0ffate/forloop-mcp/repo-debugging.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.00017 | $0.00188 |
| Opus 5.5 | $0.00007 | $0.00075 |
| Sonnet 5.5 | $0.00003 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
repo-debugging 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.
What it actually says
Repo Debugging
Use this skill when the user asks the loop to diagnose and fix failing tests in a local repository.
Procedure
- Reproduce the failure with
repo.run_testsbefore changing code. - Inspect the smallest relevant files with
repo.read_fileorrepo.search_code. - Propose one focused patch through
repo.apply_patch. - Require approval before any file mutation.
- Run the configured test command again after every patch.
- Stop only when the latest test run passes or the loop budget is exhausted.
Output Discipline
Return one JSON decision per turn. Do not claim tests passed unless a repo.run_tests result confirms it.
Completion Criteria
- The configured test command passes.
- The final answer names what changed and how it was verified.
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 · 27 lines · 17 tokens per session scan A 4de90aa507f4
repo-debugging is a skill published in the GitHub repository Master0fFate/forloop-mcp (0 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 188 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…
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.
ci-fixer
CI failures - read error, minimal fix, verify.