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/commit-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/commit-all-repos)<a href="https://agentmods.dev/skills/raffertyuy/repo-of-repos/commit-all-repos"><img src="https://agentmods.dev/badge/skills/raffertyuy/repo-of-repos/commit-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/commit-all-repos"><img src="https://agentmods.dev/badge/skills/raffertyuy/repo-of-repos/commit-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.00032 | $0.00581 |
| Opus 5 | $0.00016 | $0.00291 |
| Sonnet 5 | $0.00006 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
commit-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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit All Repos
Iterate through every sub-repo in repos/ and stage, commit, and push changes in each one individually, then do the same for the master repo last.
Order of Operations
- Sub-repos first — iterate through each directory in
repos/*/that is a git repository - Master repo last — commit root-level changes after all sub-repos are done
For Each Sub-Repo
For each directory under repos/<name>/ that is a git repository (has a .git directory):
Note: Skip
type: localentries fromrepos/repos.yaml— local source folders have no git history of their own. Their changes are committed via the root repo's/commitskill.
cdinto the repo directory- Run
git status(never use-uall) — if no changes, skip it - Run
git diffto review what changed - Run
git log --oneline -5to match that repo's commit message style - Read the sub-repo's agentic instructions if they exist (in priority order):
CLAUDE.mdin the sub-repo rootAGENTS.mdin the sub-repo root.github/copilot-instructions.mdin the sub-repo- These instructions take precedence over root-level instructions for that repo's commit
- Follow the sub-repo's commit message guidelines if they define any; otherwise fall back to the root
.claude/prompt-snippets/commit-message.md - Stage relevant files using explicit paths — never
git add -A - Create the commit
- Run
git pushto push the commit to the remote - Run
git statusto verify
For the Master Repo
After all sub-repos are committed:
- Run the
/commitskill for the root workspace (which excludesrepos/) - If there are no root-level changes, skip — don't create an empty commit
Notes
- Report a summary at the end: which repos had commits, which were skipped (clean), and any errors
- If a sub-repo has no changes, skip it silently — don't create empty commits
- If a pre-commit hook fails in a sub-repo, report the error and continue to the next repo
- Never force-push or amend existing commits in sub-repos
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 · 51 lines · 32 tokens per session scan A 54890317c0ce
commit-all-repos is a skill published in the GitHub repository raffertyuy/repo-of-repos (12 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 581 once invoked, about $0.0002 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage repo-sync on macOS for shared documents and team context. Use when asked what repo-sync does, to automatically sync a repo, add a repo to repo-sync, stop syncing or un-sync a repo, check sync health, configure repo-sync, uninstall it, or install and maintain its bundled agent skill. Ordinary one-time Git pulls…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.