Borrowing it
Nothing to install: this file belongs to MaxGfeller/open-harness. 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/MaxGfeller/open-harness/main/.agents/skills/release-local/SKILL.mdgit clone --depth 1 https://github.com/MaxGfeller/open-harnessWrote 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/maxgfeller/open-harness/release-local)<a href="https://agentmods.dev/skills/maxgfeller/open-harness/release-local"><img src="https://agentmods.dev/badge/skills/maxgfeller/open-harness/release-local.svg" alt="Measured on agentmods" 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.00021 | $0.00281 |
| Opus 5 | $0.00010 | $0.00140 |
| Sonnet 5 | $0.00004 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
release-local 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 8d 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
Run the release workflow from RELEASING.md.
Guardrails:
- Only run this on
mainunless the user explicitly wants a dry run elsewhere. - Require a clean worktree before versioning or publishing.
- Ask for confirmation before creating the release commit.
- Ask for confirmation again before starting
pnpm release:publish, because it publishes to npm, pushes the branch and tags to GitHub, and may require npm OTP entry.
Workflow:
- Run
pnpm release:statusand confirm there are pending changesets. - Run
pnpm version-packages. - Review the generated version bumps and changelog entries with the user.
- Commit the release files with
Release packagesunless the user requests a different message. - Run
pnpm release:publish. - Confirm that npm publish succeeded and that GitHub Releases were created or updated for the tags on
HEAD. - If npm publish succeeded but GitHub release creation failed, rerun
pnpm release:githubafter fixing the blocker.
If publish fails because of npm auth, OTP, or missing release notes, stop, report the exact blocker, and do not keep mutating the repo.
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.
- 8d ago First seen · 27 lines · 21 tokens per session scan A b51eedce4af7
release-local is a skill published in the GitHub repository MaxGfeller/open-harness (608 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 281 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-30.
Other skills, from other repositories
ship
Enter the Ship phase of CocoBrew. Reads review.md approval, generates structured commit, creates semantic version tag, optionally creates PR via gh CLI, and records deployment details. Requires approved review.
apply-semantic-versioning
Apply semantic versioning (SemVer 2.0.0) to determine the correct version bump based on change analysis. Covers major/minor/patch classification, pre-release identifiers, build metadata, and breaking change detection. Use when preparing a new release to determine the correct version number, after merging changes…
exit-strategy
Use when implementation is complete and all tests pass — guides the clean exit from a development branch with structured options for merge, PR, or cleanup.
create-github-release
Create a GitHub release with proper tagging, release notes, and optional build artifacts. Covers semantic versioning, changelog generation, and GitHub CLI usage. Use when marking a stable version of software for distribution, publishing a new library or application version, creating release notes for stakeholders, or…
project-release-maintainer
Project overlay for release and packaging maintenance across install layout, shipped assets, automation, license and notice alignment, and release docs. Not for content-only documentation or publishing without explicit authorization.
release-skills
A release workflow for preparing and publishing a new software version.