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.
git clone --depth 1 https://github.com/pleaseai/claude-code-pluginsWrote 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/pleaseai/claude-code-plugins/sync)<a href="https://agentmods.dev/commands/pleaseai/claude-code-plugins/sync"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/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/pleaseai/claude-code-plugins/sync"><img src="https://agentmods.dev/badge/commands/pleaseai/claude-code-plugins/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.00015 | $0.00354 |
| Opus 5 | $0.00008 | $0.00177 |
| Sonnet 5 | $0.00003 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00035 |
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 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.
What it actually says
Sync the local repository with origin. gt sync pulls trunk, prompts to delete branches that have been merged into trunk, and restacks the remaining stack onto the new trunk tip. User input: $ARGUMENTS.
Steps
- Run
git status --shortto ensure the working tree is clean. If not, ask whether to commit/stash before syncing. - Run
gt lsto capture the stack shape before sync. - Run
gt sync $ARGUMENTS(respecting any flags the user passed). - If the output reports conflicts on specific branches:
- List the conflicted branches to the user.
- For each,
gt co <branch>→gt restack→ resolve in editor →gt add .→gt continue -a. - If a restack should be aborted, run
gt abortand report.
- Run
gt lsagain so the user sees the new state and which merged branches were pruned.
Key flags
-a, --all— sync every trunk (when multiple trunks are configured)-d, --delete-all— delete merged branches without prompting-f, --force— accept all destructive prompts
When to use vs git pull
Always prefer gt sync in a Graphite-tracked repo. Plain git pull won't restack downstream branches and can leave stacks pointing at the old trunk tip, which then requires a manual gt restack.
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 · 29 lines · 15 tokens per session scan A 074ac0e7bd58
sync is a command published in the GitHub repository pleaseai/claude-code-plugins (13 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 354 once invoked, about $0.0001 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-09-07.
Other commands, from other repositories
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.
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.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
handoff
Export a Waybill Bundle by default, or import one when requested.