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 skills add gylove1994/superpowers-deepseek-v4 --skill confirming-worktree-before-editgit clone --depth 1 https://github.com/gylove1994/superpowers-deepseek-v4Wrote 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/gylove1994/superpowers-deepseek-v4/confirming-worktree-before-edit)<a href="https://agentmods.dev/skills/gylove1994/superpowers-deepseek-v4/confirming-worktree-before-edit"><img src="https://agentmods.dev/badge/skills/gylove1994/superpowers-deepseek-v4/confirming-worktree-before-edit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/gylove1994/superpowers-deepseek-v4/confirming-worktree-before-edit"><img src="https://agentmods.dev/badge/skills/gylove1994/superpowers-deepseek-v4/confirming-worktree-before-edit.svg" alt="Reviewed on agentmods" width="80" 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.00052 | $0.01500 |
| Opus 5 | $0.00026 | $0.00750 |
| Sonnet 5 | $0.00010 | $0.00300 |
| Haiku 4.5 | $0.00005 | $0.00150 |
Grade A, and why
confirming-worktree-before-edit 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 11d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Confirming Worktree Before Edit
Overview
Before modifying any file in this session, confirm whether the user wants an isolated worktree — but only once per session.
Core principle: Ask once. Record the choice. Delegate setup. Never edit before the gate when consent is still unknown.
Scope: All persistent writes to project files, including:
- Project source, configuration, and skill documents
docs/superpowers/specs/*.mddocs/superpowers/plans/*.mddocs/superpowers/brainstorms/*-brainstorm.mddocs/superpowers/brainstorms/*-plan-progress.md- Any other writable path inside the project repository (including Cursor agent-mode drafts)
Announce at start: "I'm using the confirming-worktree-before-edit skill to confirm worktree preference before editing."
Step 0: Skip Conditions
Do NOT run this gate when any of these apply:
-
Read-only mode — Ask mode or any context where file edits are technically impossible (Write/StrReplace/ApplyPatch and equivalent tools unavailable). Skip entirely. Plan mode does not skip this gate when edits are possible.
-
Subagent dispatch — If you were dispatched as a subagent (
<SUBAGENT-STOP>in using-superpowers), skip. The parent agent must run this gate before dispatching you. -
Already in a linked worktree — Run detection (same as using-git-worktrees Step 0):
GIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P)
GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P)
# Submodule guard — if this returns a path, treat as normal repo, not worktree
git rev-parse --show-superproject-working-tree 2>/dev/null
If GIT_DIR != GIT_COMMON (and not a submodule): already isolated. Record worktree consent: asked, choice: skipped (already in worktree) and proceed to Step 4.
- User already declared worktree preference — User rules, instructions, or an earlier message in this session explicitly state worktree preference (create one / work in place / use
/worktree). Honor it. Recordworktree consent: asked, choice: yes|nomatching that preference. Proceed to Step 3 or Step 4 as appropriate.
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.
- 11d ago First seen · 154 lines · 52 tokens per session scan A d33f83e88235
confirming-worktree-before-edit is a skill published in the GitHub repository gylove1994/superpowers-deepseek-v4 (10 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 1,500 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…