Borrowing it
Nothing to install: this file belongs to raffertyuy/repo-of-repos. 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/raffertyuy/repo-of-repos/main/.agents/skills/pr-all-repos/SKILL.mdgit clone --depth 1 https://github.com/raffertyuy/repo-of-reposWrote 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/raffertyuy/repo-of-repos/pr-all-repos)<a href="https://agentmods.dev/skills/raffertyuy/repo-of-repos/pr-all-repos"><img src="https://agentmods.dev/badge/skills/raffertyuy/repo-of-repos/pr-all-repos/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/raffertyuy/repo-of-repos/pr-all-repos"><img src="https://agentmods.dev/badge/skills/raffertyuy/repo-of-repos/pr-all-repos.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.00024 | $0.00876 |
| Opus 5.5 | $0.00010 | $0.00350 |
| Sonnet 5.5 | $0.00005 | $0.00175 |
| Haiku 4.5 | $0.00002 | $0.00088 |
Grade A, and why
pr-all-repos 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 2mo 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR All Repos
Create pull requests across all sub-repos that have branches ready for review, then cross-link them as sibling PRs.
Prerequisites
ghCLI must be authenticated (gh auth status)- Each sub-repo must have a remote configured
Order of Operations
- Scan — identify repos with PR-ready branches
- Create PRs — open a PR in each qualifying repo
- Cross-link — update each PR description with sibling PR URLs
Step 1: Scan
For each directory in repos/*/ that is a git repository:
- Check the current branch:
git -C repos/<name> branch --show-current - Skip if on the default branch (main/master) — nothing to PR
- Check if a PR already exists for this branch:
gh pr view --repo <remote> --json url 2>/dev/null - Skip if a PR already exists — but record its URL for cross-linking
- Check if the branch has been pushed:
git -C repos/<name> log @{u}..HEAD 2>/dev/null - If unpushed commits exist, push first:
git -C repos/<name> push -u origin <branch>
Collect the list of repos that need new PRs and repos that already have PRs.
Step 2: Create PRs
For each repo that needs a new PR:
cdinto the repo directory- Read
git log --oneline main..<branch>(or master) to understand the changes - Draft a PR title (short, under 70 characters) and body
- Create the PR:
gh pr create --title "<title>" --body "$(cat <<'EOF'
## Summary
<bullet points describing changes>
## Sibling PRs
<!-- Will be updated with cross-links -->
## Test Plan
- [ ] <testing steps>
🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
- Record the PR URL
Step 3: Cross-Link
After all PRs are created (or found existing), do a second pass:
For each PR (new and existing), update its description to include a "Sibling PRs" section listing all other PRs in this batch:
## Sibling PRs
- [frontend#42](https://github.com/org/frontend/pull/42) — Update auth UI components
- [infra#18](https://github.com/org/infra/pull/18) — Add new IAM role for auth service
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.
- 2mo ago First seen · 103 lines · 24 tokens per session scan A 2ebe4152d4ba
pr-all-repos is a skill published in the GitHub repository raffertyuy/repo-of-repos (17 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 876 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
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…