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 skills add tianhanz/ears --skill sync-and-plangit clone --depth 1 https://github.com/tianhanz/earsWrote 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/skills/tianhanz/ears/sync-and-plan)<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="Measured on agentmods" 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.00156 | $0.01516 |
| Opus 5 | $0.00078 | $0.00758 |
| Sonnet 5 | $0.00031 | $0.00303 |
| Haiku 4.5 | $0.00016 | $0.00152 |
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 8d 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 — 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.
-
Check current branch and worktree status:
git branch --show-current git worktree list git status --short -
Determine the main branch name:
git rev-parse --verify main 2>/dev/null && echo "main" || echo "master" -
Fetch and merge master into the current branch:
git fetch origin git merge origin/<main-branch> --no-editIf there are merge conflicts, stop and report them — do not auto-resolve. List the conflicting files and let the user decide how to proceed.
-
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/
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.
- 8d ago First seen · 158 lines · 156 tokens per session scan A cde271ed867a
sync-and-plan is a skill published in the GitHub repository tianhanz/ears (5 stars, last pushed 4mo ago), licensed MIT. It adds 156 tokens to every session and 1,516 once invoked, about $0.0008 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.