Borrowing it
Nothing to install: this file belongs to egregore-labs/egregore. 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/egregore-labs/egregore/main/.claude/skills/sync-repos/SKILL.mdgit clone --depth 1 https://github.com/egregore-labs/egregoreWrote 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/egregore-labs/egregore/sync-repos)<a href="https://agentmods.dev/skills/egregore-labs/egregore/sync-repos"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/sync-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/egregore-labs/egregore/sync-repos"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/sync-repos.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 21 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00043 | $0.00806 |
| Opus 5.5 | $0.00017 | $0.00322 |
| Sonnet 5.5 | $0.00009 | $0.00161 |
| Haiku 4.5 | $0.00004 | $0.00081 |
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 24d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smart sync of all Egregore repos. Fetches first, only pulls if behind.
When to invoke
User says: "/sync-repos", "sync all repos", "sync everything", "get every repo up to date"
Execution boundary
This is deterministic multi-repository sync. Run it inline with bounded parallel fetches; do not spend a Loom/model-routing call or delegate it to another agent.
Repos to sync
../{memory_dir}— shared knowledge (derived frommemory_repoinegregore.json)- Any repos listed in the
reposarray inegregore.json(as sibling directories../{repo}) - Current repo (egregore-core)
Read egregore.json first to get the dynamic list:
# Memory repo directory
bash bin/config-get.sh memory_dir
# Managed repos
bash bin/config-get.sh repos
Use the first command’s printed value as {memory_dir} and each line from the second as a managed {repo} name; for each value, quote it in single quotes when you use it in a command, and write any single quote inside the value as '\''. If a command prints nothing, it contributes no repo to sync.
Execution
For each repo, run these commands:
# 1. Fetch (always)
git -C /path/to/repo fetch origin --quiet
# 2. Compare local vs remote
git -C /path/to/repo rev-parse HEAD
git -C /path/to/repo rev-parse origin/main
Use the printed revisions as {local_sha} and {remote_sha}. If they differ, pull and then count commits behind:
# 3. Only pull if different
git -C /path/to/repo pull origin main --quiet
# Count commits behind
git -C /path/to/repo rev-list HEAD..origin/main --count
Use the printed count as {behind} for the output. If the revisions match, report the repo as up to date and skip the pull and count.
For the current repo (egregore-core): sync the develop branch instead of main:
# Update local develop ref without switching branches (safe for concurrent sessions)
git fetch origin develop:develop --quiet
# If on dev/* branch, rebase onto develop
git branch --show-current
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.
- 24d ago Changed · +6 lines c14845b78d74
- 1mo ago First seen · 100 lines · 43 tokens per session scan A 5ff369652b20
sync-repos is a skill published in the GitHub repository egregore-labs/egregore (293 stars, last pushed 9d ago), licensed MIT. It adds 43 tokens to every session and 806 once invoked, about $0.0002 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-30.
Other skills, from other repositories
git-workflow
Git branching, commit conventions, rebase vs merge, conflict resolution, and release tagging. Use when setting up a git workflow, writing commits, resolving conflicts, or preparing a release.
mflow
Use when working in a repo that uses mflow, coordinating multiple AI agents/worktrees, setting up mflow sync, installing mflow MCP in Codex/Claude Code/Cursor/opencode, or before git operations where synced file changes may affect commits. Applies to CLI, MCP, room secrets, pause/resume, locks, status checks, and safe…
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
gh-skill
Manage agent skills with gh skill. Use this skill to discover, preview, install, update, and publish Agent Skills so an agent can self-manage the skills available in its environment.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.