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/patrickserrano/lacquerWrote 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/patrickserrano/lacquer/sync-worktree)<a href="https://agentmods.dev/commands/patrickserrano/lacquer/sync-worktree"><img src="https://agentmods.dev/badge/commands/patrickserrano/lacquer/sync-worktree/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/patrickserrano/lacquer/sync-worktree"><img src="https://agentmods.dev/badge/commands/patrickserrano/lacquer/sync-worktree.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.00200 |
| Opus 5.5 | $0.00003 | $0.00080 |
| Sonnet 5.5 | $0.00001 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
sync-worktree 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 1mo 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.
What it actually says
Safely update the current worktree with latest changes from main.
Prerequisites
- Must be in a git worktree (not the main working directory)
- Working directory should be clean (no uncommitted changes)
Steps
- Verify we're in a worktree:
git worktree list - Check for uncommitted changes:
git status --porcelain - If changes exist, warn user and STOP
- Fetch latest:
git fetch origin main - Rebase current branch onto main:
git rebase origin/main - Report result
On Conflict
If rebase conflicts occur:
- Report conflicting files
- Abort rebase:
git rebase --abort - Suggest manual resolution or merge strategy
Safety
- Never force push
- Never modify main branch
- Always preserve local commits
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.
- 1mo ago First seen · 34 lines · 7 tokens per session scan A 8c67aa4198f2
sync-worktree is a command published in the GitHub repository patrickserrano/lacquer (4 stars, last pushed 2d ago), licensed MIT. It adds 7 tokens to every session and 200 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-31.
Other commands, from other repositories
align
Context-aware alignment. In plan mode it audits the active plan and folds the amendments in. Otherwise it reviews the branch, a named branch, or a pull request against Ion's principles, authors a fix plan, and after approval implements and commits the fixes.
squash
Rebuild a feature branch into clean conventional commits while preserving its exact final tracked tree.
create-issue
Open a GitHub issue on the Ion repo for a bug or feature request derived from the current conversation, with consumer project details scrubbed.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
resolve-dependabot-prs
Triage open Dependabot PRs, return a quick risk/action summary table, then enter planning mode with an ordered rebase→merge→follow-up→resume resolution plan.
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.