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/klausfreiberufler/devflow-mcp/devflow-worktreesnpx skills add KlausFreiberufler/devflow-mcp --skill devflow-worktreesgit clone --depth 1 https://github.com/KlausFreiberufler/devflow-mcpWhat 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.00069 | $0.01239 |
| Opus 5 | $0.00034 | $0.00620 |
| Sonnet 5 | $0.00014 | $0.00248 |
| Haiku 4.5 | $0.00007 | $0.00124 |
Grade A, and why
devflow-worktrees 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: devflow-worktrees
Port of Superpowers
using-git-worktrees. The skill that keeps each flow's working state physically separate so the agent never accidentally edits main's checkout while another flow's branch is in flight.
When to use
- After
flow_update planning→approval(i.e. when enteringreadyorin_progressfor the first time on this flow). - When picking up an existing flow whose worktree already exists — verify the path, switch into it, do not re-create.
Path convention
.claude/worktrees/<displayId>-<slug>
Examples:
DF-289-hook-1-discipline-tokens→.claude/worktrees/DF-289-hook-1-discipline-tokensDF-292-verification-gate-self-approval→.claude/worktrees/DF-292-verification-gate-self-approval
Slug rules: lowercase, hyphenated, max 40 chars, drop stop-words. Match the branch-slug if a feature branch already exists.
Process
1 · Check for an existing worktree
git worktree list | grep <displayId>
ls .claude/worktrees/
If one exists for this flow → switch into it, run a quick git status sanity check, continue. Do not create a duplicate.
2 · Create a new worktree
# from the main checkout (project root)
BRANCH="feature/<displayId-lower>-<slug>" # or hotfix/...
DIR=".claude/worktrees/<displayId>-<slug>"
git worktree add -b "$BRANCH" "$DIR" main
cd "$DIR"
Verify:
git statusshows the new branch.- The worktree directory contains the project (
ls -la). node_modulesis shared via the parent — re-install only if needed (typically not).
3 · Work in the worktree
All edits, commits, tests, branch-pushes happen from within the worktree. The main checkout stays clean — useful for parallel flows or quick gh pr view lookups without checking out a different branch.
4 · Cleanup on done
When the flow reaches done (PR merged or work abandoned):
# from the project root, NOT from inside the worktree
cd <project-root>
git worktree remove .claude/worktrees/<displayId>-<slug>
# if the branch is gone (squash-merged), prune the leftover ref:
git fetch --prune
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 · 129 lines · 69 tokens per session scan A a13ee4fa1137
devflow-worktrees is a skill published in the GitHub repository KlausFreiberufler/devflow-mcp (1 stars, last pushed 3d ago), licensed MIT. It adds 69 tokens to every session and 1,239 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…