sync-repos

sync-repos is a command for coding agents from rios0rios0/guide. It costs 0 tokens per session (299 once invoked), scanned A, original, MIT.

A command that synchronizes Git repositories found inside a directory, including pulling updates and preserving unfinished work.

In plain words
What is it for?
Use it to update all nested repositories, fetch and rebase their default branches, and restore each repository's original branch afterward.
Why use it?
It reduces the manual effort of updating many repositories while protecting uncommitted changes on temporary work-in-progress branches.

Command

Install

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.

agentmods
npx agentmods add commands/rios0rios0/guide/sync-repos
Clone the repo
git clone --depth 1 https://github.com/rios0rios0/guide

Wrote 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.

agentmods badge for sync-repos

README.md
[![agentmods](https://agentmods.dev/badge/commands/rios0rios0/guide/sync-repos.svg)](https://agentmods.dev/commands/rios0rios0/guide/sync-repos)
Your own site
<a href="https://agentmods.dev/commands/rios0rios0/guide/sync-repos"><img src="https://agentmods.dev/badge/commands/rios0rios0/guide/sync-repos.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 299 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00299
Opus 5 $0.00000 $0.00150
Sonnet 5 $0.00000 $0.00060
Haiku 4.5 $0.00000 $0.00030

Measured 4d ago against content hash 19d62dd74e9f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sync-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 4d 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.

.github/workflows/generate-ai-rules/commands/sync-repos.md · 22 lines

What it actually says

Sync all git repositories found recursively under the current directory (or a given path). For each repo discovered via find -name .git -type d:

  1. If the repo has uncommitted changes (staged, unstaged, or untracked), create a WIP branch (wip/auto-stash-<timestamp>) and commit all changes with message wip: auto-stash uncommitted changes.
  2. Checkout the default branch (detected via git symbolic-ref refs/remotes/origin/HEAD, fallback to main).
  3. Run git fetch --all --prune and git pull --rebase.
  4. If pull/rebase fails, abort the rebase and restore the previous branch.
  5. Restore the original branch (or WIP branch if changes were stashed).

Run this by executing the shell function:

source ~/.scripts/linux-engineering-git-sync-repos.sh && git-sync-repos

When no argument is given, it defaults to the current working directory ($PWD). If the user provides a specific subdirectory (e.g. dev.azure.com/ContosoSecurity), pass it as argument:

source ~/.scripts/linux-engineering-git-sync-repos.sh && git-sync-repos "$HOME/Development/dev.azure.com/ContosoSecurity"

Print the summary at the end showing total repos, synced, WIP commits, and failures.

Changes

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.

  1. 4d ago First seen · 22 lines · 0 tokens per session scan A 19d62dd74e9f

Subscribe to this mod's changes

sync-repos is a command published in the GitHub repository rios0rios0/guide (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 299 tokens. 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.