Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/thatrebeccarae/claude-marketingnpx agentmods add skills/thatrebeccarae/claude-marketing/sync-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/thatrebeccarae/claude-marketing/sync-repos)<a href="https://agentmods.dev/skills/thatrebeccarae/claude-marketing/sync-repos"><img src="https://agentmods.dev/badge/skills/thatrebeccarae/claude-marketing/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/thatrebeccarae/claude-marketing/sync-repos"><img src="https://agentmods.dev/badge/skills/thatrebeccarae/claude-marketing/sync-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.00042 | $0.01732 |
| Opus 5 | $0.00021 | $0.00866 |
| Sonnet 5 | $0.00008 | $0.00346 |
| Haiku 4.5 | $0.00004 | $0.00173 |
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 9d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Repos
Manage public/private repository pairs. Verify parity between a dev (private) repo and its public counterpart, detect drift, run sync scripts, validate results, and ensure no PII or secrets leak to the public side.
Install
claude install-skill https://github.com/thatrebeccarae/claude-skills/tree/main/sync-repos
When to Use
- Before pushing a public repo — verify the sync is clean and current
- After major dev work — check whether the public repo has drifted behind
- On a periodic cadence — weekly or before releases, catch unsynced changes early
- When setting up a new public/private repo pair for the first time
Usage
/sync-repos check [dev-path] [public-path]— Compare repos and report drift/sync-repos sync [dev-path] [public-path]— Run sync script and validate/sync-repos setup [dev-path] [public-path]— Create initial sync-public.sh and config
If paths are omitted, prompt the user for them. Look for .syncignore or scripts/sync-public.conf in the dev repo to auto-detect the pair.
Procedure
Check Mode
-
Validate paths. Confirm both paths exist and contain
.git/directories. Abort with a clear message if either is not a git repo. -
Detect sync script. Look for
scripts/sync-public.sh,scripts/sync-public.conf, or.syncignorein the dev repo. Report whether a sync mechanism exists. -
Compare file lists. Generate sorted file lists for both repos (excluding
.git/,node_modules/,dist/). Categorize differences:- Expected exclusions — files matching known exclusion patterns (see Common Exclusion Patterns below) or listed in
.syncignore/sync-public.conf - Unexpected drift — files present in dev but missing from public that are NOT in any exclusion list
- Diverged files — files present in both repos but with different content (compare via
sha256sumorgit hash-object) - Public-only files — files in public but not in dev (legitimate: README, CONTRIBUTING, LICENSE, .github/)
- Expected exclusions — files matching known exclusion patterns (see Common Exclusion Patterns below) or listed in
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 146 lines · 42 tokens per session scan A 1e79d3285c4b
sync-repos is a skill published in the GitHub repository thatrebeccarae/claude-marketing (137 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 1,732 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-09-03.
Other skills, from other repositories
pr
Creates GitHub PR after pre-flight checks (lint/typecheck/tests), structured summary from commits. Triggers: pr, pull request, create PR, ready to merge.
git-mastery
Advanced Git: rebase, bisect, reflog, cherry-pick, worktrees, LFS. Triggers: rebase, bisect, cherry-pick, reflog, force push, merge conflict, worktree.
rollback
Rolls back git commit, DB migration, or deploy to known-good with safety + health checks. Triggers: rollback, revert deploy, revert migration, rollback commit, git revert.
deploy
Deploys with pre-flight checks and health verification. Triggers: deploy, deployment, ship, release, push to prod.
commit
Creates Conventional Commits with pre-commit validation. Triggers: commit, conventional commit, git commit, message.
edit-discipline
Change files with the edit and write tools, never by rewriting them through bash (sed, awk, tee, heredoc, redirection), and show git diff before reporting a file-changing task as done. Triggers: edit, write, modify, refactor, patch, fix, diff, review changes.