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 agents/41fred/ace-level1/workspace-syncgit clone --depth 1 https://github.com/41fred/ace-level1What 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.00233 | $0.03865 |
| Opus 5 | $0.00117 | $0.01932 |
| Sonnet 5 | $0.00047 | $0.00773 |
| Haiku 4.5 | $0.00023 | $0.00386 |
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 yesterday.
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 — 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.
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.
- yesterday First seen · 340 lines · 233 tokens per session scan A 8b499294374c
workspace-sync is an agent published in the GitHub repository 41fred/ace-level1 (5 stars, last pushed 1mo ago), licensed MIT. It adds 233 tokens to every session and 3,865 once invoked, about $0.0012 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.