MARVIN is a personal AI assistant built to remember conversations, track goals, organize work, and connect to external applications. People use it as a chief-of-staff-style extension for Claude Code or GitHub Copilot CLI, with integrations including Google Workspace, Microsoft 365, Slack, Linear, Notion, and Telegram. The catalogue entries provide commands, agents, skills, and instructions that define MARVIN's workflows.
Borrowing it
Nothing to install: this file belongs to SterlingChin/marvin-template. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SterlingChin/marvin-template/main/.claude/commands/sync.mdgit clone --depth 1 https://github.com/SterlingChin/marvin-templateWrote 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/sterlingchin/marvin-template/sync)<a href="https://agentmods.dev/commands/sterlingchin/marvin-template/sync"><img src="https://agentmods.dev/badge/commands/sterlingchin/marvin-template/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.
<a href="https://agentmods.dev/commands/sterlingchin/marvin-template/sync"><img src="https://agentmods.dev/badge/commands/sterlingchin/marvin-template/sync.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.00007 | $0.00994 |
| Opus 5.5 | $0.00003 | $0.00398 |
| Sonnet 5.5 | $0.00001 | $0.00199 |
| Haiku 4.5 | $0.00001 | $0.00099 |
Grade A, and why
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 2mo 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sync - Get Updates
Pull new features and commands from the MARVIN template into your workspace.
Instructions
1. Find the Template
Read .marvin-source to get the path to the template directory:
cat .marvin-source
If this file doesn't exist, tell the user:
"I can't find your template source. This usually means you set up MARVIN manually. Would you like to tell me where your template folder is?"
2. Check Version
Compare versions between the user's workspace and the template:
USER_VERSION=$(cat VERSION 2>/dev/null || echo "0.0.0")
TEMPLATE_VERSION=$(cat {template}/VERSION 2>/dev/null || echo "unknown")
echo "Current: $USER_VERSION"
echo "Template: $TEMPLATE_VERSION"
Replace {template} with the path from .marvin-source.
If versions are the same, tell the user:
"You're on the latest version ($USER_VERSION). No updates available."
And stop (unless the user explicitly asked to check files anyway).
If versions differ, extract what changed from the template's CHANGELOG.md.
Read {template}/CHANGELOG.md and collect all entries between the user's
version and the template's version. Show a summary:
You're on {USER_VERSION}. Template is at {TEMPLATE_VERSION}.
What's new:
{bullet points from CHANGELOG entries}
Checking for new files...
Then proceed to step 3.
If the user has no VERSION file (pre-versioning install), treat as 0.0.0 and show all CHANGELOG entries.
3. Check What's New
Compare the template's files with the user's workspace:
Files to sync:
.claude/commands/- Slash commands.claude/agents/- Subagent definitions.claude/skills/- Reusable skillsdocs/patterns/- Architectural pattern docs
Files to NEVER sync (user's data):
state/- User's goals and current statesessions/- Session logsreports/- Weekly reportscontent/- User's contentmeetings/- User's meeting notespersonal/- User's personal filesCLAUDE.md- User's profile (contains personal config).env- User's secrets.marvin-team/- User's team config (if present)
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.
- 2mo ago First seen · 141 lines · 7 tokens per session scan A 1a07c9b3ec50
sync is a command published in the GitHub repository SterlingChin/marvin-template (1,024 stars, last pushed 2mo ago), licensed MIT. It adds 7 tokens to every session and 994 once invoked, about $0.0000 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-30.
Other commands, from other repositories
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.