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/emaraschio/cursor-commands/git-sync-workspacegit clone --depth 1 https://github.com/emaraschio/cursor-commandsWhat 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.00555 |
| Opus 5 | $0.00015 | $0.00278 |
| Sonnet 5 | $0.00006 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
git-sync-workspace 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 2d 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
Overview
Discover git repos in a Cursor multi-root workspace, preflight each one, and sync clean repos to their remote default branch. Skips dirty or unsafe repos with a clear report. Full workflow: .cursor/skill-contracts/git-sync-workspace/SKILL.md (user install: ~/.cursor/skill-contracts/git-sync-workspace/SKILL.md).
Defaults
| Setting | Default |
|---|---|
| Dirty repos | Skip and report (no writes) |
| Pull strategy | --ff-only |
| Fetch | --all --prune |
| Concurrency | ≤ 6 parallel fetches |
Steps
- Read
.cursor/skill-contracts/git-sync-workspace/SKILL.mdfor the full agent contract; if that file is missing, read~/.cursor/skill-contracts/git-sync-workspace/SKILL.md. - Execute phases in order (Discover → Preflight → Sync → Report); do not skip preflight or modify dirty repos.
- Report the workspace summary (Synced / Skipped / Failed).
Anti-patterns
- Never sync over a dirty working tree. Trigger: a repo has uncommitted changes. Wrong: checking out or pulling over the dirty tree, or running
git reset --hardto force it. Correct: skip the repo, recordskipped_dirty, and continue the others. Reason: overwriting a dirty tree can destroy uncommitted work that is not recoverable. - Do not force-push default branches. Reason: force-pushing a shared default branch can erase teammates' commits and rewrite published history.
- Do not guess repo paths. Trigger: workspace discovery yields nothing. Wrong: scanning arbitrary directories like
~/code/*without direction. Correct: ask the user which paths to include. Reason: syncing repos the user did not intend can disrupt unrelated work.
Examples
/git-sync-workspace/git-sync-workspacewith "only sync repo1 and repo2"
Maintainers
Behavioral eval: .cursor/skill-contracts/git-sync-workspace/eval/cases.md. Ship gate sections: A, S before changing SKILL.md or this command.
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.
- 2d ago First seen · 45 lines · 30 tokens per session scan A 8f7af4b2a045
git-sync-workspace is a command published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 26d ago), licensed MIT. It adds 30 tokens to every session and 555 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 commands, from other repositories
grok_execute
Explicitly turn the task-local Grok executor mode on or off.
thirdparty-web-interface-guidelines
Review these files for compliance: $ARGUMENTS.
plan
Research, clarify requirements, and produce an approved implementation plan before writing code (Cursor Plan Mode).
green-repo
Drive the whole repository to a verified-green baseline — typecheck, lint, tests, build — with authorized fixing of pre-existing debt.
ship-and-observe
Take merged, green code to a verified, monitored production release — deploy, confirm the revision is live, smoke-test, observe, and roll back if needed.
gate-logic
Audit CI/CD gate logic — silent bypass, ratchet gaming, conflicting conditions — report only.