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/ccoalm/ccl-skillsnpx agentmods add commands/ccoalm/ccl-skills/ccl-worktree-checkWrote 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/ccoalm/ccl-skills/ccl-worktree-check)<a href="https://agentmods.dev/commands/ccoalm/ccl-skills/ccl-worktree-check"><img src="https://agentmods.dev/badge/commands/ccoalm/ccl-skills/ccl-worktree-check.svg" alt="Measured on agentmods" 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.00013 | $0.00426 |
| Opus 5 | $0.00006 | $0.00213 |
| Sonnet 5 | $0.00003 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
ccl-worktree-check 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 8d 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
Check the current repository's worktree isolation state before editing.
Run the repo-local preflight first:
bash skills/worktree-isolation/scripts/worktree-status.sh --slug <task-slug>
If it prints UNSAFE, do not edit. Create the feature worktree with the printed
git worktree add -b ... command, then continue inside that new path. New lanes
default to (and are recommended to use) the primary checkout root at
.work/worktrees/<task-slug>; per-lane local metadata is conventionally
.work/lanes/<task-slug>.json and the status script only prints the snippet/path
(it does not write metadata). The .work/worktrees location is a convention, not
a hard safety condition: an existing independent feature worktree outside it can
still report SAFE when the hard conditions hold (independent worktree, named
feature branch, not a submodule, not detached, clean tree, confirmed base); in
that case the script only emits a non-blocking warning suggesting .work/worktrees
for new lanes.
If the script is missing, fallback to:
git status --short --branch
git rev-parse --show-toplevel
git rev-parse --git-dir
git rev-parse --git-common-dir
git symbolic-ref --quiet --short HEAD || true
test -f .worktree-only && printf '.worktree-only present\n' || printf '.worktree-only absent\n'
If .worktree-only is present and the current checkout is main or master with git-dir == git-common-dir, stop and create a feature worktree before editing. Manual fallback creation should anchor on the primary checkout root, derived from the parent of git rev-parse --git-common-dir, e.g. git worktree add -b <branch> <primary-root>/.work/worktrees/<slug> <base>.
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.
- 8d ago First seen · 37 lines · 13 tokens per session scan A 8365d991a47e
ccl-worktree-check is a command published in the GitHub repository ccoalm/ccl-skills (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 13 tokens to every session and 426 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-08-31.
Other commands, from other repositories
epic-sync
Sync epic issue bodies, labels, and local coordination snapshots from GitHub.
commit-push-pr
An automated Git workflow that checks a project, synchronizes documentation, commits changes, and can create or merge a GitHub pull request. A pull request is a request for teammates to review and add changes to a shared codebase.
auto
An automated coding workflow runs a software task from planning through code changes, checks, and a pull request. A pull request is a proposed change for review before it is merged into the main codebase.
sync
A command that pulls the latest code from the main Git branch and updates the project's key planning and instruction documents to match it.
pull
A quick command that downloads the latest commits from the main Git branch into the current project.
worktree-cleanup
A command for removing a Git worktree, which is a separate working folder linked to the same repository, after its pull request is merged.