agentmods.dev

sync-and-plan

sync-and-plan is a skill for Claude Code from tianhanz/ears. It costs 156 tokens per session (1,516 once invoked), scanned A, original, MIT.

A project catch-up and planning tool for repositories developed across multiple worktrees, which are separate working copies of one project.

In plain words
What is it for?
Use it when syncing with the main branch, checking what changed, finding TODOs, or planning the next steps.
Why use it?
It gathers branch updates, coordination records, trace fragments, and unfinished tasks so you can understand the current state before choosing work.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions Claude Code.

not rated 6repo 6mo ago A scan 156 tokens original MIT

Good fit Use it when syncing with the main branch, checking what changed, finding TODOs, or planning the next steps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tianhanz/ears/sync-and-plan
View source ↗ tianhanz/ears
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.

Any agent
npx skills add tianhanz/ears --skill sync-and-plan
Clone the repo
git clone --depth 1 https://github.com/tianhanz/ears

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.

agentmods badge for sync-and-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/tianhanz/ears/sync-and-plan/github.svg)](https://agentmods.dev/skills/tianhanz/ears/sync-and-plan)
Your own site
<a href="https://agentmods.dev/skills/tianhanz/ears/sync-and-plan"><img src="https://agentmods.dev/badge/skills/tianhanz/ears/sync-and-plan/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.

agentmods 80×15 button for sync-and-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/tianhanz/ears/sync-and-plan"><img src="https://agentmods.dev/badge/skills/tianhanz/ears/sync-and-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 156 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,516 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00156 $0.01516
Opus 5.5 $0.00062 $0.00606
Sonnet 5.5 $0.00031 $0.00303
Haiku 4.5 $0.00016 $0.00152

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

Security

Grade A, and why

sync-and-plan 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.

skills/sync-and-plan/SKILL.md · 158 lines

How it starts

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

Sync and Plan

Orient yourself in a multi-worktree project: pull the latest from master, read what happened across all branches, and surface actionable next steps.

This skill exists because the project is developed by multiple independent Claude Code sessions in separate git worktrees. Each session has its own context and can't see what others are doing. Running this skill at the start of a session (or after being away) closes that visibility gap fast.

The argument provided is: $ARGUMENTS

Step 1 — Pull updates from master

Sync the current branch with the latest master so you're working on top of the most recent code.

  1. Check current branch and worktree status:

    git branch --show-current
git worktree list
git status --short

  2. Determine the main branch name:

    git rev-parse --verify main 2>/dev/null && echo "main" || echo "master"

  3. Fetch and merge master into the current branch:

    git fetch origin
git merge origin/<main-branch> --no-edit

    If there are merge conflicts, stop and report them — do not auto-resolve. List the conflicting files and let the user decide how to proceed.

  4. Show what came in:

    git log --oneline HEAD@{1}..HEAD   # new commits pulled in

Step 2 — Read the trace index

The trace index (trace/master.md) is a reverse-chronological log of everything merged to master. Read it to understand what happened recently.

cat trace/master.md

Summarize the most recent 3-5 merge entries for the user, focusing on:

  • What features/fixes were added
  • Which branches delivered them
  • Any patterns (e.g., "three branches all touched the chrome extension this week")

Step 3 — Read coordination state across all worktrees

Each worktree publishes its status to .claude/coordination/state/<branch>.json. These files contain what the branch is doing, what files it touches, and what it plans to do next.

ls .claude/coordination/state/

Read the full file on GitHub · 158 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.

  1. 2mo ago First seen · 158 lines · 156 tokens per session scan A cde271ed867a

Subscribe to this mod's changes

sync-and-plan is a skill published in the GitHub repository tianhanz/ears (6 stars, last pushed 6mo ago), licensed MIT. It adds 156 tokens to every session and 1,516 once invoked, about $0.0006 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.

PlanningProject management
Related

sync-and-plan compared with skills from other repositories

sync-and-plan next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
sync-and-plantianhanz/earsSkill66mo agoMITA156Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill314k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143ktodayMITA103Claude Code