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 manhvann/codexkit --skill worktreegit clone --depth 1 https://github.com/manhvann/codexkitWrote 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/manhvann/codexkit/worktree)<a href="https://agentmods.dev/skills/manhvann/codexkit/worktree"><img src="https://agentmods.dev/badge/skills/manhvann/codexkit/worktree.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00018 | $0.00757 |
| Opus 5 | $0.00009 | $0.00378 |
| Sonnet 5 | $0.00004 | $0.00151 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
ck: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 4d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Worktree
Create an isolated git worktree for parallel feature development.
Workflow
Step 1: Get Repo Info
node .agents/skills/worktree/scripts/worktree.cjs info --json
Parse JSON response for: repoType, baseBranch, projects, worktreeRoot, worktreeRootSource.
Step 2: Detect Branch Prefix
From user's description:
- "fix", "bug", "error", "issue" →
fix - "refactor", "restructure", "rewrite" →
refactor - "docs", "documentation", "readme" →
docs - "test", "spec", "coverage" →
test - "chore", "cleanup", "deps" →
chore - "perf", "performance", "optimize" →
perf - Default →
feat
Step 3: Convert to Slug
"add authentication system" → add-auth
"fix login bug" → login-bug
Max 50 chars, kebab-case.
Step 4: Handle Monorepo
If repoType === "monorepo" and project not specified, use ask the user:
ask the user({
questions: [{
header: "Project",
question: "Which project for the worktree?",
options: projects.map(p => ({ label: p.name, description: p.path })),
multiSelect: false
}]
})
Step 5: Execute
Monorepo:
node .agents/skills/worktree/scripts/worktree.cjs create "<PROJECT>" "<SLUG>" --prefix <TYPE>
Standalone:
node .agents/skills/worktree/scripts/worktree.cjs create "<SLUG>" --prefix <TYPE>
Options:
--prefix- Branch type: feat|fix|refactor|docs|test|chore|perf--worktree-root <path>- Override default location (only if needed)--json- JSON output--dry-run- Preview
Step 6: Install Dependencies
Based on project context, run in background:
bun.lock→bun installpnpm-lock.yaml→pnpm installyarn.lock→yarn installpackage-lock.json→npm installpoetry.lock→poetry installrequirements.txt→pip install -r requirements.txtCargo.toml→cargo buildgo.mod→go mod download
Commands
| Command | Usage | Description |
|---|---|---|
create |
create [project] <feature> |
Create worktree |
remove |
remove <name-or-path> |
Remove worktree |
info |
info |
Repo info with worktree location |
list |
list |
List worktrees |
What ships with it
2 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.
- 4d ago First seen · 97 lines · 18 tokens per session scan A 279a891a0e78
ck:worktree is a skill published in the GitHub repository manhvann/codexkit (88 stars, last pushed 9d ago), licensed MIT. It adds 18 tokens to every session and 757 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-09-03.
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.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".