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.
npx agentmods add commands/benkapner/claude-code-basecamp/repo-syncgit clone --depth 1 https://github.com/Benkapner/claude-code-basecampWrote 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/commands/benkapner/claude-code-basecamp/repo-sync)<a href="https://agentmods.dev/commands/benkapner/claude-code-basecamp/repo-sync"><img src="https://agentmods.dev/badge/commands/benkapner/claude-code-basecamp/repo-sync.svg" alt="Measured on agentmods" 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 | $0.00030 | $0.00452 |
| Opus 5 | $0.00015 | $0.00226 |
| Sonnet 5 | $0.00006 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
repo-sync 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 3d 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.
What it actually says
Repo Sync Check
Check focused repositories for sync freshness with the remote.
Instructions
1. Identify Focused Repos
Determine which repositories to check:
- If repos are selected via
/focus, check those - If no repos are focused, check the repo the user is currently working in
- If no repo context is available, ask the user which repo to check
2. Fetch and Check Each Repo
For each repo, run:
cd repositories/<name>
git fetch --quiet
Then check behind count:
git rev-list --count HEAD..@{u} 2>/dev/null || echo "no upstream"
And check for uncommitted changes:
git status --porcelain
3. Report Results
If behind the remote:
Repository
<name>is N commits behindorigin/<branch>. Want me to pull the latest changes?
If user accepts:
git pull --rebase origin <branch>
If uncommitted changes exist:
Repository
<name>has uncommitted changes:
Show the output of git status --short.
Consider committing or stashing before pulling.
If both behind AND dirty:
Show both warnings. Recommend stash → pull → unstash or commit → pull.
If up to date and clean:
Repository
<name>is up to date with remote. No uncommitted changes.
4. Summary
If checking multiple repos, end with a summary:
Repo Sync Summary
=================
repo-a: UP TO DATE
repo-b: 3 commits behind (offered to pull)
repo-c: UP TO DATE, 2 uncommitted changes
Arguments
$ARGUMENTS can be:
- A repo name or path (e.g.,
laborrepositories/lab) — check that repo specifically - Empty — check all focused 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.
- 3d ago First seen · 85 lines · 30 tokens per session scan A f32af8a4e222
repo-sync is a command published in the GitHub repository Benkapner/claude-code-basecamp (16 stars, last pushed 14d ago), licensed MIT. It adds 30 tokens to every session and 452 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-30.
Other commands, from other repositories
spec-forge
Use when generating software specifications — full chain (Idea→Decompose→Tech Design + Feature Specs) or individual documents.
propagate
Use after editing an upstream doc (PRD/SRS/tech-design/feature-spec) to propagate changes downstream and keep the entire doc chain consistent.
analyze
Use when analyzing a document collection to map themes, find conflicts, gaps, and redundancies — generates landscape analysis report.
review
Use when reviewing spec-forge generated documents for quality, completeness, and consistency — auto-fixes issues if found.
audit
Use when auditing existing project docs for quality, completeness, and code alignment — generates findings report with fix recommendations.
tech-design
Use when writing a tech design, architecture doc, RFC, or design document — follows Google Design Doc format.