Borrowing it
Nothing to install: this file belongs to fokkerone/superspecs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fokkerone/superspecs/main/.skills/execute-branch/SKILL.mdgit clone --depth 1 https://github.com/fokkerone/superspecsWrote 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/fokkerone/superspecs/execute-branch)<a href="https://agentmods.dev/skills/fokkerone/superspecs/execute-branch"><img src="https://agentmods.dev/badge/skills/fokkerone/superspecs/execute-branch.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.00043 | $0.00590 |
| Opus 5 | $0.00022 | $0.00295 |
| Sonnet 5 | $0.00009 | $0.00118 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
execute-branch 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 6d 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
Skill: execute-branch
You are creating an isolated execution environment for this spec.
One branch per spec. No exceptions. Isolation prevents parallel workstreams from interfering with each other.
Steps
1. Check git status
git status
git branch --show-current
Verify:
- The working directory is clean (no uncommitted changes)
- We're on the correct base branch (usually
mainordevelop)
If there are uncommitted changes, stop: "Commit or stash changes before creating a branch."
2. Determine branch name
Convention: superspec/<slug>
Examples:
superspec/auth-jwtsuperspec/export-csvsuperspec/payment-stripe
3. Choose: branch or worktree
Standard branch (default, single workstream):
git checkout -b superspec/<slug>
Git worktree (parallel workstreams, recommended when executing multiple specs simultaneously):
git worktree add ../project-<slug> -b superspec/<slug>
Ask the user: "Use a worktree for parallel execution, or a standard branch?"
If worktree: note the path in plan.md.
4. Verify branch was created
git branch --show-current
# should output: superspec/<slug>
5. Update plan.md
Add to superspec/phases/<slug>-execute/plan.md:
## Branch
Branch name: `superspec/<slug>`
Type: [branch | worktree]
Worktree path: <path if worktree, else N/A>
Created from: <base branch> @ <short SHA>
Created: <timestamp>
6. Update status.md
## Phase
2.2 — Execute › Branch ✅
## Checklist
...
- [x] Branch created (superspec/<slug>)
...
7. Handoff
Branch ready: superspec/<slug>
Type: <branch/worktree>
Base: <base-branch> @ <SHA>
Next: /superspecs:subagent <slug>
Output
- Git branch
superspec/<slug>created superspec/phases/<slug>-execute/plan.mdupdated with branch info- Updated
superspec/specs/<slug>/status.md
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.
- 6d ago First seen · 103 lines · 43 tokens per session scan A 0fc743fcb6ae
execute-branch is a skill published in the GitHub repository fokkerone/superspecs (4 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 590 once invoked, about $0.0002 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.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
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".