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/careerchain-ys/stdd/remove-worktreenpx skills add careerchain-ys/stdd --skill remove-worktreegit clone --depth 1 https://github.com/careerchain-ys/stddWrote 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/skills/careerchain-ys/stdd/remove-worktree)<a href="https://agentmods.dev/skills/careerchain-ys/stdd/remove-worktree"><img src="https://agentmods.dev/badge/skills/careerchain-ys/stdd/remove-worktree.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 | $0.00133 | $0.00762 |
| Opus 5 | $0.00067 | $0.00381 |
| Sonnet 5 | $0.00027 | $0.00152 |
| Haiku 4.5 | $0.00013 | $0.00076 |
Grade A, and why
remove-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 4d 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
Worktree破棄スキル
現在のセッションで使用しているworktree環境を自動特定して破棄する。
1. 現在のworktree番号を自動判定
以下のコマンドで現在のworking directoryを確認する:
pwd
worktree-Nの形式が含まれていれば、N がINSTANCE_ID- そうでない場合(プロジェクトの main worktree 等)は、Environment情報の "Additional working directories" を確認し、
worktree-NにマッチするものからINSTANCE_IDを特定する - 複数ある場合はユーザーに確認する
2. 稼働中のworktreeと関連コンテナを確認
for i in 1 2 3 4; do
dir="../worktree-${i}"
if [ -d "$dir" ]; then
branch=$(git -C "$dir" branch --show-current 2>/dev/null || echo "不明")
container=$(docker ps -a --filter "label=devcontainer.local_folder=$(cd "$dir" && pwd)" --format "{{.Names}} ({{.Status}})" 2>/dev/null || echo "なし")
echo " worktree-${i}: ブランチ=${branch}, コンテナ=${container:-なし}"
fi
done
3. 未コミット・未プッシュの変更を確認
特定したINSTANCE_IDを使って確認する:
git -C "../worktree-<INSTANCE_ID>" status
git -C "../worktree-<INSTANCE_ID>" log <primary_branch>..HEAD --oneline 2>/dev/null # <primary_branch> = .stdd.config.yml の project.primary_branch
4. 破棄を実行
./scripts/remove-worktree.sh -i <INSTANCE_ID>
デフォルトではDockerイメージを保持して次回の起動を高速化する。
--clean を付けるとイメージも含めて完全削除する。
5. 破棄後の確認
docker images --format "table {{.Repository}}\t{{.Tag}}\t{{.Size}}" | grep -E "REPOSITORY|vsc-<project_name>"
docker volume ls --format "table {{.Name}}" | grep -E "NAME|<project_name>|dind"
注意事項
- 未コミットの変更がないか事前に確認すること
- コミット済みだがpush未完了のブランチがないか確認すること
- デフォルトではDockerイメージは保持される(次回起動の高速化のため)
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.
- 4d ago First seen · 67 lines · 133 tokens per session scan A 939cdc871e7f
remove-worktree is a skill published in the GitHub repository careerchain-ys/stdd (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 133 tokens to every session and 762 once invoked, about $0.0007 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…