kickoff-branch

A workflow for starting coding work in an isolated Git worktree and feature branch after checking that the default branch is clean and tests pass.

In plain words
What is it for?
Use it when beginning a feature or task, especially when you need a new branch or worktree and a verified starting point.
Why use it?
It prevents development directly on the main branch and catches existing failures before new changes are made.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/danielvm-git/bigpowers/kickoff-branch
Any agent
npx skills add danielvm-git/bigpowers --skill kickoff-branch
Clone the repo
git clone --depth 1 https://github.com/danielvm-git/bigpowers

Made for: Claude Code, Codex.

Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,497 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00058 $0.01497
Opus 5 $0.00029 $0.00749
Sonnet 5 $0.00012 $0.00299
Haiku 4.5 $0.00006 $0.00150

Measured 3d ago against content hash b808c07296f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

kickoff-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 3d 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.

.cline/skills/kickoff-branch/SKILL.md · 144 lines

How it starts

The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.

story: e51s03

story: e20s03

Kickoff Branch

HARD GATE — Direct work on main or master is PROHIBITED. Every task MUST start with this skill to create a feature branch or worktree.

HARD GATE — Do NOT proceed with development until Preflight passes on the default branch. Red Preflight blocks branch creation and all forward work — invoke quick-fix or fix-bug per CONVENTIONS § Discovered Defects.

Create an isolated working environment before touching any code. Preflight must be green before you write feature code — solo-default owns the whole tree, not just the current task diff.

Process

1. Confirm task name

Ask if not already known: "What's the name of this feature or task?" Use it as the branch name slug (kebab-case, max 40 chars).

2. Anchor on default branch (main or master)

HARD GATE — Kickoff MUST start from an updated, clean default branch in the primary repository root (not a linked worktree).

# Detect default branch
DEFAULT=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo main)

git checkout "$DEFAULT"
git pull --ff-only origin "$DEFAULT"   # skip if no remote
git status                             # working tree MUST be clean
git log --oneline -5

Spec-only pre-kickoff — before enforcing the clean-tree gate, check whether dirty files are spec artifacts:

DIRTY=$(git status --porcelain | awk '{print $2}')
NON_SPEC=$(echo "$DIRTY" | grep -v '^specs/' || true)

if [ -z "$DIRTY" ]; then
  : # clean — proceed
elif [ -z "$NON_SPEC" ]; then
  # spec-only dirty tree — offer auto-commit
  echo "Dirty spec artifacts: $(echo $DIRTY | tr '\n' ' ')"
  read -p "Commit spec artifacts before kickoff? [Y/n]: " CONFIRM
  CONFIRM=${CONFIRM:-Y}
  if [[ "$CONFIRM" =~ ^[Yy] ]]; then
    git add specs/
    git commit -m "chore(state): checkpoint before kickoff"
  fi
else
  echo "Dirty tree: $NON_SPEC (not a spec artifact). Stash or commit before proceeding."
  exit 1
fi

Read the full file on GitHub · 144 lines

Changes

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.

  1. 3d ago First seen · 144 lines · 58 tokens per session scan A b808c07296f4

Subscribe to this mod's changes

kickoff-branch is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 26d ago), licensed MIT. It adds 58 tokens to every session and 1,497 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-30.