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 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/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/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="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.00130 | $0.01369 |
| Opus 5.5 | $0.00052 | $0.00548 |
| Sonnet 5.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 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.
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.
- 2mo 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 (6 stars, last pushed 3d ago), licensed MIT. It adds 130 tokens to every session and 1,369 once invoked, about $0.0005 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 skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.