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/release-branchnpx skills add danielvm-git/bigpowers --skill release-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.00063 | $0.02734 |
| Opus 5 | $0.00032 | $0.01367 |
| Sonnet 5 | $0.00013 | $0.00547 |
| Haiku 4.5 | $0.00006 | $0.00273 |
Grade A, and why
release-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 2d 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Branch
HARD GATE — Do NOT merge or release if tests fail or if coverage gates are not met. If the branch is red, return to
develop-tddto fix regressions or add missing tests before proceeding.
Finalize a completed feature branch: verify coverage gates, integrate onto main, and clean up the worktree.
Additional modes
--hotfix: Cherry-pick to main + tag. Skip PR in solo.--squash-state: Squashchore(state):commits before merge.
Integrate mode
Read specs/state.yaml key workflow_mode (team-pr | solo-git). Fall back to profiles/solo-git.md.
| Mode | When | Ship path |
|---|---|---|
| solo-local | workflow_mode: solo-git |
Auto: scripts/land-branch.sh if present, else fallback (Step 5) |
| team-pr | workflow_mode: team-pr (default) |
gh pr create → gh pr merge --squash |
If unsure, prefer solo-local.
Process
Timing:
bash scripts/bp-timing.sh start release-branchat invocation;bash scripts/bp-timing.sh end release-branchbefore handoff.
1. Final verification
<full test command> && <typecheck command> && <lint command>
git log main...HEAD --oneline | grep -vE "^[a-f0-9]+ (feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert)(\(.+\))?!?: .+$" && echo "❌ Non-conventional commits found" || echo "✅ Commits verified"
# Block AI agent attribution (P1)
git log main...HEAD --format="%B" | grep -qiE 'co[- ]authored[- ]by' && echo "❌ Co-authored-by footer found — blocked" || echo "✅ No AI attribution"
- All tests pass, no type errors, no lint violations, all commits follow Conventional Commits
- NO
Co-authored-byorCo-Authored-Byin any commit body — P1 rule (CONVENTIONS.md § Git Attribution).land-branch.shblocks the merge if found.
2. Coverage check
- Overall coverage ≥ 80%; business logic coverage ≥ 95%
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.
- 2d ago First seen · 303 lines · 63 tokens per session scan A 9d86b8ec6611
release-branch is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 25d ago), licensed MIT. It adds 63 tokens to every session and 2,734 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
devops/changelog-generation
自动生成 CHANGELOG，基于 git 提交历史和 pipeline 产物信息，遵循 Conventional Commits 和 Keep a Changelog 规范.
re0-release
Walk a pending change through this repo's shipping and releasing checklist end to end, then tag and publish once confirmed. User-invoked: run it when you've decided to ship.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog-entry
Add a new entry to CHANGELOG.yml under the current unreleased version (or create the version block if needed), then regenerate documentation. Use when the user says things like "add a changelog entry", "log this fix in the changelog", or "/changelog-entry".