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 skills add StoneReaper/openhandoff --skill openhandoff-releasegit clone --depth 1 https://github.com/StoneReaper/openhandoffWrote 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/stonereaper/openhandoff/openhandoff-release)<a href="https://agentmods.dev/skills/stonereaper/openhandoff/openhandoff-release"><img src="https://agentmods.dev/badge/skills/stonereaper/openhandoff/openhandoff-release.svg" alt="Measured on agentmods" 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.00027 | $0.00279 |
| Opus 5 | $0.00014 | $0.00139 |
| Sonnet 5 | $0.00005 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
openhandoff-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 6d 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.
What it actually says
OpenHandoff Release
Use this skill for version bumps, release candidates, changelog preparation, package builds, and GitHub release readiness.
Release checklist
-
Inspect the working tree and recent history. Preserve unrelated user changes.
-
Decide the version from user intent and compatibility impact; do not invent a breaking-version bump.
-
Update the package version, changelog, citation metadata, and user-facing docs together.
-
Run the full local checks:
python -m pytest -q python -m compileall -q src tests python -m build -
Inspect the generated wheel and sdist contents. Confirm they contain source, license, and docs but no
.context, credentials, private transcripts, or local paths. -
Summarize the release notes, test evidence, and remaining risks. Ask for explicit approval before creating a tag, GitHub release, package upload, or push.
Quality bar
- Release notes describe user-visible changes and migration impact.
- CI validates the same build path used for release artifacts.
- Security and contribution guidance remain discoverable.
- Do not inflate download, contributor, star, or dependency metrics.
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.
- 6d ago First seen · 32 lines · 27 tokens per session scan A d19a4177d0e2
openhandoff-release is a skill published in the GitHub repository StoneReaper/openhandoff (0 stars, last pushed 14d ago), licensed MIT. It adds 27 tokens to every session and 279 once invoked, about $0.0001 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-31.
Other skills, from other repositories
github-pr-merge
Merges GitHub Pull Requests after validating pre-merge checklist. Use when user wants to merge PR, close PR, finalize PR, complete merge, approve and merge, or execute merge. Runs pre-merge validation (tests, lint, CI, comments), confirms with user, merges with proper format, handles post-merge cleanup.
mx-pr
Draft a pull request from the feature spec and git log, run an autonomous commit-history cleanup (content check), then publish to GitHub, GitLab, or Bitbucket — or hand off. Use when a feature branch is ready for PR, standalone or from mx-flow. Usage: /mx-pr [name].
Finishing a Development Branch
Clean branch finalization, squashing commits, and updating changelogs before merging.
oss-launch
Use when taking a repo open source, or hardening one that already is. Run /oss-launch and it scans the repo (stack, existing files, git remote, secrets), asks only what it cannot infer, then generates a tailored OSS file collection (README, LICENSE, CONTRIBUTING, CODEOFCONDUCT, SECURITY, CHANGELOG, .gitignore…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…