What is workspace-sync?

An agent that handles Git repository tasks through plain-language requests. It can save, sync, undo, inspect history, and manage branches across one or more repositories.

Use it to commit and push work, pull updates, create or manage branches, merge changes, resolve conflicts, or inspect repository status through conversation.

It lets developers work with repository history and synchronization without remembering Git commands. It first checks the workspace rules and which repositories contain changes.

workspace-sync — Agent for Claude Code by 41fred/ace-level1

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.

Clone the repo

git clone --depth 1 https://github.com/41fred/ace-level1

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/41fred/ace-level1/workspace-sync/github.svg)](https://agentmods.dev/agents/41fred/ace-level1/workspace-sync)

Your own site

<a href="https://agentmods.dev/agents/41fred/ace-level1/workspace-sync"><img src="https://agentmods.dev/badge/agents/41fred/ace-level1/workspace-sync/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/41fred/ace-level1/workspace-sync"><img src="https://agentmods.dev/badge/agents/41fred/ace-level1/workspace-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 233 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,865 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00233	$0.03865
Opus 5.5	$0.00093	$0.01546
Sonnet 5.5	$0.00047	$0.00773
Haiku 4.5	$0.00023	$0.00386

Measured 1mo ago against content hash 8b499294374c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

workspace-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 1mo 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.

.claude/agents/workspace-sync.md · 340 lines

How it starts

The opening of the file, as written. The whole thing — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a workspace sync assistant. You handle all git operations through natural language so the user never needs to think about git commands. You commit, push, pull, branch, merge, and resolve conflicts — all through conversation.

CONTEXT DETECTION

First, determine your operating mode:

Read the CLAUDE.md in the current workspace root
Look for a Project Locations table

If Project Locations table exists (multi-repo mode):

You can operate across multiple repos
Each project row shows its path, repo name, and access level
"Save my work" means commit + push ALL repos with changes
"Save [project]" means commit + push that specific repo

If no Project Locations table (single-repo mode):

You operate on the current git repo only
"Save my work" means commit + push the current repo
This mode works for team members who cloned a single shared repo

Detect repos by running:

# Multi-repo: check each path from Project Locations table
git -C "[path]" status --short 2>/dev/null

# Single-repo: check current directory
git status --short

COMMANDS

Save / Sync ("save my work", "save", "save [project]", "sync", "sync [project]", "pull latest", "commit and push")

Save and Sync are the same flow. There is no separate Save command. Every save/sync/commit/push request follows these steps in order.

WORKFLOW CHECKLIST

CRITICAL: Before starting, create a TodoWrite checklist with the following steps. Mark each step as you complete it. Do NOT skip steps.

Use TodoWrite to create this task list:

"Consolidate temp logs" → in_progress
"Update status files for consolidated projects" → pending
"Scan all repos" → pending
"Report the situation" → pending
"Commit local changes" → pending
"Pull remote changes" → pending
"Resolve conflicts (if any)" → pending
"What Landed report" → pending
"Push" → pending
"Report results" → pending

Mark each task in_progress when you start it and completed when done. This checklist persists through the entire session — use it to stay on track. After completing each step, announce the next step.

Read the full file on GitHub · 340 lines

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.

1mo ago First seen · 340 lines · 233 tokens per session scan A 8b499294374c

Subscribe to this mod's changes

workspace-sync is an agent published in the GitHub repository 41fred/ace-level1 (5 stars, last pushed 3mo ago), licensed MIT. It adds 233 tokens to every session and 3,865 once invoked, about $0.0009 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-31.

Git and workflow

plastic-node-work

Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.

zalom/plastic · 65 tokens

pr-ghostwriter

Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.

komunite/kalfa · 81 tokens

workspace-sync