Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/bahayonghang/my-ai-cli-toolkitnpx agentmods add skills/bahayonghang/my-ai-cli-toolkit/kndoshnWrote 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/bahayonghang/my-ai-cli-toolkit/kndoshn)<a href="https://agentmods.dev/skills/bahayonghang/my-ai-cli-toolkit/kndoshn"><img src="https://agentmods.dev/badge/skills/bahayonghang/my-ai-cli-toolkit/kndoshn/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/bahayonghang/my-ai-cli-toolkit/kndoshn"><img src="https://agentmods.dev/badge/skills/bahayonghang/my-ai-cli-toolkit/kndoshn.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.00046 | $0.00700 |
| Opus 5 | $0.00023 | $0.00350 |
| Sonnet 5 | $0.00009 | $0.00140 |
| Haiku 4.5 | $0.00005 | $0.00070 |
Grade A, and why
managing-git-worktrees 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 6d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managing Git Worktrees
Safety Rules (MUST follow)
- Never discard uncommitted work - Check
git -C <path> status --porcelainbefore destructive operations - Inspect before mutate - Run
--dry-runbeforeprune,listbeforeremove - Avoid
--ignore-other-worktrees- Treat as last resort, require explicit confirmation - Quote paths with spaces - Use forward slashes
Command Reference
| Task | Command |
|---|---|
| List all | git worktree list |
| List (machine) | git worktree list --porcelain |
| Add existing branch | git worktree add <path> <branch> |
| Add new branch | git worktree add -b <new-branch> <path> <start-point> |
| Add detached | git worktree add --detach <path> <commit-ish> |
| Remove (clean only) | git worktree remove <path> |
| Prune dry-run | git worktree prune --dry-run |
| Prune | git worktree prune |
| Lock | git worktree lock <path> |
| Unlock | git worktree unlock <path> |
Workflow: Add Worktree for New Task
git worktree add -b <new-branch> ../wt/<new-branch> <start-point>
git -C ../wt/<new-branch> status
If start-point is ambiguous:
git show-ref --heads --remotes | grep <branch-name>
Workflow: Add Worktree for Existing Branch
git branch --list <branch>
git worktree list --porcelain
git worktree add <path> <branch>
Error: "branch is already checked out"
Resolution order (safest first):
- Use existing worktree - Check path via
git worktree list --porcelain - Create new branch -
git worktree add -b <new-branch> <path> <branch> - Detached HEAD -
git worktree add --detach <path> $(git rev-parse <branch>) - Force (last resort) - Requires explicit user confirmation:
git switch --ignore-other-worktrees <branch>
Workflow: Cleanup
git worktree list --porcelain
git -C <path> status --porcelain
git worktree remove <path>
git worktree prune --dry-run
git worktree prune
Locked worktree removal (requires explicit confirmation):
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.
- 6d ago First seen · 88 lines · 46 tokens per session scan A f040f12b5698
managing-git-worktrees is a skill published in the GitHub repository bahayonghang/my-ai-cli-toolkit (16 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 700 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
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.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.