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 agentmods add skills/mayank-io/mstack/finish-work-on-local-worktreenpx skills add mayank-io/mstack --skill finish-work-on-local-worktreegit clone --depth 1 https://github.com/mayank-io/mstackWrote 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/mayank-io/mstack/finish-work-on-local-worktree)<a href="https://agentmods.dev/skills/mayank-io/mstack/finish-work-on-local-worktree"><img src="https://agentmods.dev/badge/skills/mayank-io/mstack/finish-work-on-local-worktree.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.00130 | $0.01369 |
| Opus 5 | $0.00065 | $0.00685 |
| Sonnet 5 | $0.00026 | $0.00274 |
| Haiku 4.5 | $0.00013 | $0.00137 |
Grade A, and why
finish-work-on-local-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 5d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finish Work on Local Worktree
Complete a worktree lifecycle: squash-merge the branch into main, update all related documentation status, update the project plan, and recommend what to work on next.
Prerequisites
- All tests pass on the worktree branch
- No uncommitted changes in the worktree
- Work on the branch is verified and ready to integrate
Arguments
Accept an optional branch name argument. If not provided, detect from the current worktree or ask the user.
Workflow
Execute these phases in order. Stop and report if any phase fails.
Phase 1: Local Merge
Invoke the git-worktree:local-merge skill via the Skill tool, passing the branch name if provided as an argument.
Wait for the merge to complete before proceeding. If the merge fails (conflicts, dirty worktree, not in a worktree), stop and help the user resolve the issue.
After the merge succeeds, note the BRANCH name — it drives doc discovery in Phase 2.
Phase 2: Update Related Documentation
Find all docs related to the merged branch and update their status to completed.
Step 2a: Find related docs
Use the Grep tool to search docs/ for files whose YAML frontmatter contains work: <BRANCH> (substituting the actual branch name from Phase 1). Also check the related: frontmatter array in those docs to find transitively related docs.
Step 2b: Update frontmatter status
For each related doc found:
- Read the current
status:andstage:frontmatter fields - If
status:is not alreadycompleted, update it tocompleted - If
stage:exists, update it toimpl(implementation is done) - Do NOT change docs that are already
completedorarchived
Step 2c: Report changes
List each doc updated with its old and new status:
Updated docs:
- docs/2026-04-04-feature-design.md: active → completed
- docs/2026-04-04-feature-impl-plan.md: active → completed
Phase 3: Update Project Plan
Find and update the project plan to reflect the completed milestone. If no project plan is found, skip this phase entirely and note in the final report that no project plan was updated.
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.
- 5d ago First seen · 146 lines · 130 tokens per session scan A 75536779eb18
finish-work-on-local-worktree is a skill published in the GitHub repository mayank-io/mstack (5 stars, last pushed 11d ago), licensed MIT. It adds 130 tokens to every session and 1,369 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…