Borrowing it
Nothing to install: this file belongs to Codename-11/SubFrame. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Codename-11/SubFrame/main/.agents/skills/release/SKILL.mdgit clone --depth 1 https://github.com/Codename-11/SubFrameWrote 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/skills/codename-11/subframe/release)<a href="https://agentmods.dev/skills/codename-11/subframe/release"><img src="https://agentmods.dev/badge/skills/codename-11/subframe/release/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/skills/codename-11/subframe/release"><img src="https://agentmods.dev/badge/skills/codename-11/subframe/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00017 | $0.01228 |
| Opus 5.5 | $0.00007 | $0.00491 |
| Sonnet 5.5 | $0.00003 | $0.00246 |
| Haiku 4.5 | $0.00002 | $0.00123 |
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 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Procedure
Create a release for SubFrame. The argument specifies the version bump type or an explicit version number.
Dynamic Context
Current version (from package.json):
!node -e "console.log(require('./package.json').version)"
Last 5 tags:
!git tag --sort=-v:refname | head -5
Recent commits (last 30):
!git log --oneline --no-decorate -30
Current branch:
!git branch --show-current
Working tree clean?
!git status --porcelain
Instructions
Argument: $ARGUMENTS
Pre-flight Checks
- Verify clean working tree — if there are uncommitted changes, STOP and warn the user. Releases must be made from a clean state.
- Verify on main branch — warn if not on
main. - Verify build succeeds — run
npm run buildand confirm it completes without errors.
Step 1: Determine Version
Parse the argument:
patch— bump PATCH, keep-betasuffix (e.g.,0.2.0-beta→0.2.1-beta)minor— bump MINOR, reset PATCH, keep-betasuffix (e.g.,0.2.1-beta→0.3.0-beta)major— bump MAJOR, reset MINOR+PATCH, drop-betato produce first stable release (e.g.,0.3.0-beta→1.0.0)stable— strip-betasuffix without changing version numbers (e.g.,0.3.0-beta→0.3.0)x.y.zorx.y.z-beta(explicit) — use as-is, validate it's greater than current- No argument — analyze the commits since last tag and recommend a bump:
- Any
feat!,fix!, orBREAKING CHANGE-> MAJOR (goes stable) - Any
feat-> MINOR - Only
fix/docs/perf/chore/refactor-> PATCH - Ask the user to confirm before proceeding
- Any
Beta versioning scheme: All 0.x.y versions use the -beta suffix (no numeric counter). The -beta suffix is preserved on patch/minor bumps and only dropped when going stable via major or stable.
Step 2: Update package.json
Update the "version" field in package.json to the new version string. This is the single source of truth — FRAME_VERSION in src/shared/frameConstants.js reads from it automatically via require().
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 118 lines · 17 tokens per session scan A ea6d65173c4f
release is a skill published in the GitHub repository Codename-11/SubFrame (10 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 1,228 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-08-31.
Other skills, from other repositories
intuitive-port-worktree
Port commits or patches between worktrees when explicitly requested; preserve the target branch and unrelated edits.
intuitive-squash
Safely rewrite noisy local history into reviewable commits, with aggressive or moderate plan choices, when the user explicitly asks to squash.
changelog
A tool for writing release notes from a structured record of changes that actually shipped. Release notes summarize changes for people who use or maintain the product.
ship
Fully automated ship workflow. Merges the base branch, runs tests, audits coverage, reviews the diff, generates a CHANGELOG entry, bumps the version, commits, pushes, and creates the PR. Use when asked to "ship", "create a PR", or "open a pull request".
dev-updates
Detect and summarize uncommitted git changes grouped by feature area, then generate a structured commit message. Use when the user says "what's the update?", "what changed?", "summarize my changes", "what have I done?", or "what did I update?".
goal-release
Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the Homebrew formula from the published release assets. Use when the user wants to draft and merge a release in one go, or…