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 iowarp/clio-kit --skill clio-kit-worktree-creategit clone --depth 1 https://github.com/iowarp/clio-kitWrote 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/iowarp/clio-kit/clio-kit-worktree-create)<a href="https://agentmods.dev/skills/iowarp/clio-kit/clio-kit-worktree-create"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/clio-kit-worktree-create/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/iowarp/clio-kit/clio-kit-worktree-create"><img src="https://agentmods.dev/badge/skills/iowarp/clio-kit/clio-kit-worktree-create.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.00090 | $0.01642 |
| Opus 5.5 | $0.00036 | $0.00657 |
| Sonnet 5.5 | $0.00018 | $0.00328 |
| Haiku 4.5 | $0.00009 | $0.00164 |
Grade C, and why
clio-kit-worktree-create scanned grade C with 1 finding 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 9d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- When finished, merge using `worktree-merge` and close out using `branch-closeout`. Never remove worktrees via `rm -rf`; always use `git worktree remove`. In canonical-main-only repositories, maintainer worktree branche How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Host compatibility
This copy is adapted from Clio Coder. Apply the procedure using the current host's available tools and the user's authorized scope. The tool names, /skill invocations, .clio-coder paths, fleets, approval gates and completion gates below describe Clio Coder; they are not installed or enforced by this skill in another host. Use the host's actual skill invocation and equivalent tools. If no equivalent exists, report the missing capability. Do not assume a tool is unavailable merely because the original headless workflow says so. A referenced agent or skill must be installed before relying on it. Scientific MCPs must be configured separately.
Adapted skills use the clio-kit- prefix to distinguish them from upstream audited skills. For a companion skill named below, select its clio-kit- copy from this collection; native agents, fleets and external programs retain their original names.
Worktree Create
Stand up isolated git worktrees, each on its own branch, ready for immediate development and validation: gitignored configuration copied, dependencies installed, and health checks verified. Everything is detected from the repository; nothing about the tech stack is assumed.
See worktree setup for package manager detection, configuration files, and health checks.
Arguments
Arguments are passed in the user invocation message. Interpret them structurally from the prompt:
/skill:clio-kit-worktree-create [--base ref] [--root path] [--setup auto|none] <branch...>
Examples
/skill:clio-kit-worktree-create feat/user-profiles feat/billing-portal/skill:clio-kit-worktree-create --base main --root .worktrees feat/api-v2/skill:clio-kit-worktree-create --setup none chore/refactor-docs
Positional Arguments
<branch...>: One or more branch names to create and check out.- Required. If omitted, prompt the user for the list of branches; never guess or invent branch names.
- Validation: Each branch must be a valid ref name (
git check-ref-format --branch <branch>).
What ships with it
4 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.
- 9d ago First seen · 121 lines · 90 tokens per session scan C 52e5981663a5
clio-kit-worktree-create is a skill published in the GitHub repository iowarp/clio-kit (30 stars, last pushed 8d ago), licensed BSD-3-Clause. It adds 90 tokens to every session and 1,642 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-08.
Other skills, from other repositories
pr-to-main
A pull-request workflow for submitting feature or bug-fix changes to the main branch in a pnpm and Changesets monorepo. A monorepo stores multiple related packages in one repository, while Changesets records release information.
pr-to-main-cleanup
A cleanup tool for deleting feature branches after their pull request has been merged into the main branch. A branch is a separate line of development in a code repository.
issue-management
Create, update, list and search GitHub issues and PRs, list a repository's labels, run milestones, and check for duplicates.
release-management
Tag a commit, publish a GitHub release, and read, correct or withdraw the tags and releases already there.
pr-analysis
Analyse a GitHub pull request by fetching its metadata, diff, linked issues and CI status.
pr-management
Manage the lifecycle of a GitHub PR - create, update the description, assign, refresh the branch and merge.