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/pull-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/pull-all-repos)<a href="https://agentmods.dev/skills/raffertyuy/repo-of-repos/pull-all-repos"><img src="https://agentmods.dev/badge/skills/raffertyuy/repo-of-repos/pull-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/pull-all-repos"><img src="https://agentmods.dev/badge/skills/raffertyuy/repo-of-repos/pull-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.01878 |
| Opus 5 | $0.00012 | $0.00939 |
| Sonnet 5 | $0.00005 | $0.00376 |
| Haiku 4.5 | $0.00002 | $0.00188 |
Grade A, and why
pull-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 12d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Workspace
Read repos/repos.yaml at the project root and ensure all declared repositories and local source folders are present and up to date.
Order of Operations
- Parse
repos/repos.yaml— read therepos:list - Clone missing git repos — for each
type: git(or unset type) entry whererepos/<name>/doesn't exist, clone it - Pull existing git repos — for each git entry where
repos/<name>/already exists, fetch and pull - Verify local entries — for each
type: localentry, verifyrepos/<name>/exists on disk - Detect and register orphans — find directories in
repos/not in the manifest, auto-detect type, analyze, and add torepos/repos.yaml - Sync .gitignore — ensure each git repo has an ignore entry; local entries must NOT be in
.gitignore - Regenerate repos.md — update
repos/repos.mdwith current repo/folder analysis
Parsing repos/repos.yaml
Read repos/repos.yaml from the project root. Each entry has:
name(required) — directory name underrepos/type(optional, default:git) —"git"or"local"url(required for git, ignored for local) — git clone URLbranch(optional, default:main, git only) — branch to trackprefix(optional) — short prefix for the repo (used in references)description(optional) — one-line summary
If repos/repos.yaml has an empty list (repos: []), skip steps 2–4 and proceed directly to step 5 (orphan detection). The manifest being empty does NOT mean the workspace is empty — there may be repos on disk that need to be registered.
Cloning Missing Git Repos
For each entry where type is git (or unset) and repos/<name>/ does NOT exist:
- Run
git clone <url> repos/<name> - If a
branchis specified and it's not the default, rungit -C repos/<name> checkout <branch> - Report: cloned successfully or error
Pulling Existing Git Repos
For each entry where type is git (or unset) and repos/<name>/ already exists:
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.
- 12d ago First seen · 164 lines · 24 tokens per session scan A 87f8fbf54247
pull-all-repos is a skill published in the GitHub repository raffertyuy/repo-of-repos (12 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 1,878 once invoked, about $0.0001 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 skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…