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 commands/hmj1026/dhpk/git-worktreegit clone --depth 1 https://github.com/hmj1026/dhpkWhat 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 | $0.00014 | $0.00344 |
| Opus 5 | $0.00007 | $0.00172 |
| Sonnet 5 | $0.00003 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00034 |
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
Contract
Use for worktree lifecycle operations; do not remove or prune a worktree without confirmation. See the command contract. Stop when a branch/path is missing or dirty; completion reports exact commands and resulting status.
Context
- Worktrees: !
git worktree list 2>/dev/null || echo 'not in a git repo' - Branch: !
git rev-parse --abbrev-ref HEAD
Task
Follow the git-worktree skill workflow.
Sub-commands
| Sub-command | Action |
|---|---|
add |
Create new worktree (ask for branch + purpose) |
list |
Show all worktrees with status |
remove |
Remove a worktree (with confirmation) |
prune |
Clean up stale worktree records |
| (none) | Show current worktrees and suggest actions |
Naming
Use wt-{repo-shortname}-{purpose} format, placed in repo's parent directory.
Output
For add: the exact git worktree add command and next steps.
For list: formatted table of worktrees.
For remove: confirmation prompt then git worktree remove command.
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 First seen · 44 lines · 14 tokens per session scan A 6fa0c28a5935
git-worktree is a command published in the GitHub repository hmj1026/dhpk (2 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 344 once invoked, about $0.0001 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 commands, from other repositories
delegate-review
Run OCR in delegation mode — OCR handles file selection and rules, the host agent performs the actual review.
publish-skill
Sync a marketplace skill to the documentation site. Creates skill detail pages (EN/ZH), updates the marketplace index, and updates docs.json navigation.
star
Use the roster below to route a research-workflow request to exactly one STAR skill.
demo-command
Example slash command that wraps the demo-skill. Showcases the command kind.
discover
Search the Everruns(Dev) API catalog for available operations.
execute
Run an Everruns(Dev) workflow that can modify platform state.