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/aegntic/cldcde/worktree-creategit clone --depth 1 https://github.com/aegntic/cldcdeWhat 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.00000 | $0.00149 |
| Opus 5 | $0.00000 | $0.00075 |
| Sonnet 5 | $0.00000 | $0.00030 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
worktree-create 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 2d 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
Create a git worktree for parallel development on a separate branch without stashing.
Steps
- Verify the current repository supports worktrees:
- Determine the worktree configuration:
- Create the worktree:
- Set up the worktree environment:
- List active worktrees with
git worktree list. - Provide the path and instructions to switch to the new worktree.
Format
Worktree Created:
Path: <absolute path>
Branch: <branch name>
Base: <parent branch>
Rules
- Always create worktrees outside the main repository directory.
- Use descriptive branch names following project conventions.
- Do not copy .env files with secrets to worktrees.
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.
- 2d ago First seen · 30 lines · 0 tokens per session scan A 5fafc64a8569
worktree-create is a command published in the GitHub repository aegntic/cldcde (11 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 149 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-30.
Other commands, from other repositories
smoke
Deploy a versioned preview, hit smoke endpoints, print a status table.
seed
Load fixture teams + products into the local D1 database.
migrate
Apply pending D1 migrations to local (default) or remote.
deploy-preview
Build + deploy a versioned preview; print the preview URL.
scriptwriter-draft
Create a writers' room with a seed prompt and (optionally) contribute the first scene. Co-brainstorm space with signed contributions and a live SSE stream for peers.
scriptwriter-draw
Draw a random chaos card from the 13-card deck — a plot-twist prompt the user can use as a scene seed, a basistext for an RRR cascade, or a riff for a room contribution.