Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/danielvm-git/bigpowersnpx agentmods add rules/danielvm-git/bigpowers/kickoff-branchWrote 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/rules/danielvm-git/bigpowers/kickoff-branch)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/kickoff-branch"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/kickoff-branch/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/rules/danielvm-git/bigpowers/kickoff-branch"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/kickoff-branch.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.00031 | $0.01585 |
| Opus 5.5 | $0.00012 | $0.00634 |
| Sonnet 5.5 | $0.00006 | $0.00317 |
| Haiku 4.5 | $0.00003 | $0.00159 |
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 1mo 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
story: e51s03
story: e20s03
story: e82s02
Kickoff Branch
HARD GATE — Direct Git work on
main/masteror reuse of an unrelated Jujutsu change is prohibited. Create a feature branch/worktree or Jujutsu workspace/change.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-fixorfix-bugper CONVENTIONS § Discovered Defects.
Create an isolated Git worktree or Jujutsu workspace before code. Preflight must be green first — solo-default owns the whole tree.
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. Select the VCS procedure
Read state.yaml vcs.kind. For jj, do not run the Git blocks below: verify with jj status and jj log -r '::@' -n 5, create isolation with jj workspace add ../<task-slug> -r @, then run jj -R ../<task-slug> describe -m "feat: <task>". Record the new stable change ID. For git, continue below.
2a. Anchor Git on the default branch (main or master)
HARD GATE — Git 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
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.
- 1mo ago First seen · 148 lines · 31 tokens per session scan A f75049567414
kickoff-branch is a cursor rule published in the GitHub repository danielvm-git/bigpowers (267 stars, last pushed 27d ago), licensed MIT. It adds 31 tokens to every session and 1,585 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other cursor rules, from other repositories
pudo-optimize
Use when reviewing, verifying, or preparing changes for release.
no-auto-commit
Never commit or push without explicit user instruction.
fork-first-methodology
A development rule for projects built by copying an existing project, commonly called a fork. It requires running the original project first, defining what will change, and keeping changes as small as possible.
pull-request-changelist-instructions
Guidelines for creating consistent pull request changelists in markdown format with proper code block formatting.
git-workflow
Git workflow: commits, branches, PRs, history management.
gitflow
A set of rules for using the Gitflow development workflow, which organizes work through branches such as main, develop, and supporting feature branches.