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 hmj1026/dhpk --skill git-worktreegit clone --depth 1 https://github.com/hmj1026/dhpkWrote 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/hmj1026/dhpk/git-worktree)<a href="https://agentmods.dev/skills/hmj1026/dhpk/git-worktree"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/git-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/hmj1026/dhpk/git-worktree"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/git-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.00063 | $0.00545 |
| Opus 5.5 | $0.00025 | $0.00218 |
| Sonnet 5.5 | $0.00013 | $0.00109 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
git-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 yesterday.
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
Git Worktree
Workflow
Run from the consumer repository. Resolve one sub-command and preserve
[add|list|remove|prune] [--branch <name>] [--base <ref>]. Inspect
git worktree list --porcelain and the current branch first. Resolve every
target path and branch explicitly; a missing branch/path or dirty relevant
worktree stops the operation.
Use native Git operations only. add uses the repository parent and the
wt-{repo-shortname}-{purpose} naming convention, then reports the exact
git worktree add command and next steps. list reports each worktree and
status. remove and prune preview their exact targets and require explicit
confirmation before mutation; never use a force option to bypass a dirty
check. The detailed command sequence is in
references/workflow.md.
When NOT to Use
- A merge, rebase, branch deletion, or remote operation is requested.
- The target worktree is missing, ambiguous, or dirty.
- Removal or pruning has not received explicit confirmation.
Output
add: exact command, created path, branch, and next steps.list: a formatted table derived from native worktree records.remove/prune: confirmation state, exact target/command, and resulting status; no confirmation meansNOT_RUN.- Missing or dirty targets and native Git failures are terminal failures.
Verification
- Every target path and branch was resolved before a write.
- Relevant worktrees were checked with
git status --porcelain. - Remove/prune has explicit confirmation, or no mutation was attempted.
- Final
git worktree list --porcelainevidence matches the report.
References
references/workflow.md— native commands, naming, dirty checks, confirmation, and output details.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · +2 lines f36326f905e3
- 23d ago First seen · 53 lines · 63 tokens per session scan A 8da543f3d80e
git-worktree is a skill published in the GitHub repository hmj1026/dhpk (2 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 545 once invoked, about $0.0003 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-09-24.
Other skills, from other repositories
avatar-contribution-pr
Turn an avatar GitHub issue (from the in-app avatar-editor easter egg) into a merged sprite — validate the art, then either add a new module or replace an existing one, and open a PR that closes the issue. Handles both "Avatar contribution: " (a brand-new sprite) and "Avatar edit: " (a hand-redraw of an existing…
release
Release a new version of the mumei repository. Invoke when the user gives an explicit release instruction ("release it", "/release", "patch release", "ship 0.2.0"). Takes no argument or "patch" / "minor" / "major" for a SemVer bump, or a direct version such as "0.2.0". Wraps any uncommitted changes into a single…
generator-fix-integrator
Internal Auto-Harness generator skill for worktree-merge fix integration. Use only inside the parallel Generator integrator when it is addressing named defects from QA or retest.
open-code-review
Performs AI-powered code review on Git changes using the ocr CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply…
update-pr
Update an existing pull request with new changes. Use when the user wants to update a PR, push follow-up changes to a PR, refresh a PR description, or sync a PR with latest commits. Triggers on: update pr, update-pr, update the pr, push to pr, refresh pr, sync pr, update pull request.
merge-prep
Pre-merge analysis and preparation. Analyzes source branch vs target branch: commit stats, conflict detection, file impact. Analysis-only v1 — outputs report + suggested commands, does not auto-merge. Use when: user says 'merge prep', 'pre-merge', 'merge analysis', or /merge-prep.