Borrowing it
Nothing to install: this file belongs to vpeetla-ai/multi-agent-system-pattern. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vpeetla-ai/multi-agent-system-pattern/main/.cursor/skills/repo-fix-pr/SKILL.mdgit clone --depth 1 https://github.com/vpeetla-ai/multi-agent-system-patternWrote 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/vpeetla-ai/multi-agent-system-pattern/repo-fix-pr)<a href="https://agentmods.dev/skills/vpeetla-ai/multi-agent-system-pattern/repo-fix-pr"><img src="https://agentmods.dev/badge/skills/vpeetla-ai/multi-agent-system-pattern/repo-fix-pr/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/vpeetla-ai/multi-agent-system-pattern/repo-fix-pr"><img src="https://agentmods.dev/badge/skills/vpeetla-ai/multi-agent-system-pattern/repo-fix-pr.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.00063 | $0.00343 |
| Opus 5 | $0.00032 | $0.00171 |
| Sonnet 5 | $0.00013 | $0.00069 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
repo-fix-pr scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST https://loopforge-api.onrender.com/api/repo-fix \ Copies of this mod
1 near-identical copy found in the catalogue:
- repo-fix-pr — 100% identical, 0 lines differ
What it actually says
Repo Fix → PR Workflow
Flow
clone → scan (pytest) → orchestrate → code → review → quality
→ git checkout -b loopforge/fix-{run_id} → commit → push branch → GitHub PR
API
curl -X POST https://loopforge-api.onrender.com/api/repo-fix \
-H "Content-Type: application/json" \
-d '{"repo_url":"https://github.com/org/repo.git","task":"Fix failing tests","create_pr":true}'
Env (Render)
GROQ_API_KEY— live LLMGITHUB_TOKEN— fine-grained PAT: Contents + Pull requests write
Rules
- Never push to
main - Branch:
loopforge/fix-{run_id[:12]} - PR body includes run_id, review score, test status
Extending
src/loop_engine/workspace/git_ops.py— clone, branch, PR APIsrc/loop_engine/graph/repo_nodes.py— patch parse, quality gate- Add project detectors (npm, cargo) beside pytest
Demo
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.
- 9d ago First seen · 47 lines · 63 tokens per session scan A 257c58ab5887
repo-fix-pr is a skill published in the GitHub repository vpeetla-ai/multi-agent-system-pattern (2 stars, last pushed 5d ago), licensed MIT. It adds 63 tokens to every session and 343 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ci-triage
Diagnose failing CI, build, release-gate, or test runs for Cool Workflow. Use when a GitHub Actions check, local npm test, npm run build, release gate, smoke test, or generated-manifest check fails and Codex must identify the first actionable failure with logs and verifier commands.
spec-code-review
Structured code review for bugs, regressions, tests, and standards. Report-only by default; apply fixes only when the current user or upstream caller explicitly requests review-and-fix. mode:agent is always report-only.
spec-debug
Diagnosis loop for bugs and failing behavior. Use for errors, stack traces, regressions, failed tests, issue-tracker bugs, stuck investigations after failed fixes, or asks to debug/fix a bug.
spec-test-browser
Run browser tests on pages affected by current PR or branch.
spec-dogfood
Hands-off, diff-scoped browser QA of the active branch or PR. Use when a branch needs autonomous user-flow dogfooding before review or shipping: map changed flows, drive agent-browser, fix small breakages with regression tests, record human-decision blockers, and write a durable report. Do not use for collaborative UI…
python-testing
Guidelines for writing and running tests in the Agent Framework Python codebase. Use this when creating, modifying, or running tests.