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/danielvm-git/bigpowers/kickoff-branchnpx skills add danielvm-git/bigpowers --skill kickoff-branchgit clone --depth 1 https://github.com/danielvm-git/bigpowersWhat 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.00058 | $0.01497 |
| Opus 5 | $0.00029 | $0.00749 |
| Sonnet 5 | $0.00012 | $0.00299 |
| Haiku 4.5 | $0.00006 | $0.00150 |
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.
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
mainormasteris 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-fixorfix-bugper 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
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.
- 3d ago First seen · 144 lines · 58 tokens per session scan A b808c07296f4
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.
Other skills, from other repositories
pm/competitive-analysis
竞品调研和分析方法,通过系统性分析竞品的功能、体验和策略,发现差异化机会.
macrothink
User-invoked read-only pass for checking whether the current direction is tunnel-visioned: strip the session's bait, fan out 2 to 5 same-model fresh reads, and report divergence first without treating convergence as proof.
nba
Read the live cycle state and return the single highest-leverage next best action, not a menu. Use when a project is between phases, the author asks what to do next, too many valid threads are open, or the work needs re-entry into frame, build, drive, re0-memo, hate, re0-work, or ship.
bmad-dev-story
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan".
bmad-domain-research
Conduct domain and industry research. Use when the user says "lets create a research report on [domain or industry]".
harness-engineering
Use when an agent workflow needs production-like runtime controls for context, tools, permissions, observability, scheduling, evaluation, recovery, or maintenance.