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 skills/deancourse/git-worktree-demo/git-worktree-designnpx skills add deancourse/git-worktree-demo --skill git-worktree-designgit clone --depth 1 https://github.com/deancourse/git-worktree-demoWhat 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.00098 | $0.02230 |
| Opus 5 | $0.00049 | $0.01115 |
| Sonnet 5 | $0.00020 | $0.00446 |
| Haiku 4.5 | $0.00010 | $0.00223 |
Grade A, and why
Git Worktree Design 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 251 lines · 98 tokens per session scan A 361afd14ada6
Git Worktree Design is a skill published in the GitHub repository deancourse/git-worktree-demo (89 stars, last pushed 6mo ago), with no licence file. It adds 98 tokens to every session and 2,230 once invoked, about $0.0005 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-30.
Other skills, from other repositories
flow
Orchestrator for Ticket-Flow — default is --local (all phases in this session with user checkpoints). --parallel works multiple ready tickets at once via worktree-isolated subagents in this session; --serial (one subagent at a time, merge+deploy+cleanup per ticket) and --loop (re-query the ready queue after every…
init
Scaffold a ticket-flow project — one-time setup; trigger on "setz ticket-flow auf", "richte das Projekt für ticket-flow ein", "set up ticket-flow here". Runs bd init with tf's agents template (keeps Claude Code's own memory system), scaffolds spec dirs and worktree settings, migrates an existing KANBAN.md into beads.…
pickup
Internal phase 1 of ticket-flow, normally invoked by ticket-flow:flow — validate Definition of Ready, create (or adopt) the ticket's isolated worktree, set the branch lock, claim the item atomically → In Progress. Invoke directly only for recovery, or when the user explicitly wants just the claim+worktree step. Args…
spec
Draft a spec document for a tracked ticket before implementation — the entry point when the user describes a need in prose: "ich brauche …", "mach die spec", "schreib eine Spec für X", "wir sollten X bauen", "draft a spec". Captures the WHAT plus acceptance criteria and proposes open decisions with recommendations.…
implement
Internal phase 2 of ticket-flow, normally invoked by ticket-flow:flow — execute the plan for the claimed ticket inside its worktree: incremental commits, typecheck/test after each major step. Invoke directly only to continue implementing a ticket that is already picked up.
publish
Everything that makes this repository more public than it is — and the inspection that must run first. Report the publication state (local, private, public), run the offline preflight over the whole history, perform the guarded transition to public, or create the remote repo in the first place (first-time gh repo…