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/bugroger/beastmode/releasenpx skills add BugRoger/beastmode --skill releasegit clone --depth 1 https://github.com/BugRoger/beastmodeWhat 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.00039 | $0.02308 |
| Opus 5 | $0.00019 | $0.01154 |
| Sonnet 5 | $0.00008 | $0.00462 |
| Haiku 4.5 | $0.00004 | $0.00231 |
Grade A, and why
release 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release
Detect version, categorize commits, generate changelog, commit, merge or PR, tag.
Guiding Principles
- Bump type auto-detected, not user-prompted — commit message conventions determine major/minor/patch automatically
- Warn-and-continue for non-blocking failures — report problems, attempt fixes, only hard-stop on critical validation failures
Phase 1: Execute
1. Stage Uncommitted Changes
Stage all uncommitted changes from implement/validate phases so they're included in the squash merge.
git add -A
Report: "All changes staged. Ready for release."
2. Determine Version Bump Type
# List commits on this feature branch for bump detection
last_tag=$(git describe --tags --abbrev=0 2>/dev/null || echo "v0.0.0")
git log ${last_tag}..HEAD --oneline
Detect version bump type from commit messages:
- Any
BREAKING CHANGEor!:suffix → major bump - Any
feat:orfeat(prefix → minor bump - Otherwise → patch bump
Important: Do NOT read plugin.json for the current version — the worktree's copy is stale. The actual version bump happens post-merge on main in the checkpoint phase.
Use the auto-detected bump type without asking.
3. Categorize Commits
last_tag=$(git describe --tags --abbrev=0 2>/dev/null || echo "v0.0.0")
git log ${last_tag}..HEAD --oneline
Group commits by type:
- Breaking Changes —
BREAKING CHANGE,!:suffix - Features —
feat:orfeat( - Fixes —
fix:orfix( - Docs —
docs:ordocs( - Chores —
chore:,refactor:,ci:,build:
4. Generate Release Notes
Save to .beastmode/artifacts/release/YYYY-MM-DD-<epic-name>.md using the Release Notes Template (see Reference section).
Omit empty sections (e.g., no Breaking Changes → skip that heading).
Use **Bump:** major|minor|patch instead of a concrete version — the actual version is computed post-merge from main's current state.
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 · 313 lines · 39 tokens per session scan A 85fc5b948668
release is a skill published in the GitHub repository BugRoger/beastmode (16 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 2,308 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…