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.
git clone --depth 1 https://github.com/CaptainMe-AI/lead-dev-osWrote 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/commands/captainme-ai/lead-dev-os/create-worktree)<a href="https://agentmods.dev/commands/captainme-ai/lead-dev-os/create-worktree"><img src="https://agentmods.dev/badge/commands/captainme-ai/lead-dev-os/create-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/commands/captainme-ai/lead-dev-os/create-worktree"><img src="https://agentmods.dev/badge/commands/captainme-ai/lead-dev-os/create-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.00000 | $0.00129 |
| Opus 5.5 | $0.00000 | $0.00052 |
| Sonnet 5.5 | $0.00000 | $0.00026 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
create-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 1mo 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.
What it actually says
Follow these steps to create a git worktree.
-
Get the current project's folder name.
-
Create a folder adjacent to the current project's folder and name it {current project folder name}-worktrees. For example, if the current project folder is named myapp, create folder called myapp-worktrees. Both myapp and myapp-worktrees should have the same parent folder.
-
Create a git worktree and branch named $ARGUMENTS from the main project folder and save it inside the {current project folder name-worktrees folder that was created.
-
cd into the new $ARGUMENTS worktree folder
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.
- 1mo ago First seen · 13 lines · 0 tokens per session scan A fceede2df375
create-worktree is a command published in the GitHub repository CaptainMe-AI/lead-dev-os (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 129 tokens. 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
gh-release
Create a new release for the marketplace or a specific plugin.
gh-merge
Merge an approved pull request with standardized settings.
gh-review
Review a pull request with proper branch checkout and convention checks.
flow
Universal workflow entry point. Use /flow for skill-driven GitHub development. Verbs: start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue.
gh-pr
Create a pull request with full code review, quality gates, and reviewer suggestions.
gh-start
Complete workflow from issue assignment through implementation. Ends with option to create PR via /gh-pr or continue working.