Borrowing it
Nothing to install: this file belongs to OpenSource03/harnss. 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/OpenSource03/harnss/master/.agents/skills/release/SKILL.mdgit clone --depth 1 https://github.com/OpenSource03/harnssWrote 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/opensource03/harnss/release)<a href="https://agentmods.dev/skills/opensource03/harnss/release"><img src="https://agentmods.dev/badge/skills/opensource03/harnss/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/opensource03/harnss/release"><img src="https://agentmods.dev/badge/skills/opensource03/harnss/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.00054 | $0.01226 |
| Opus 5.5 | $0.00022 | $0.00490 |
| Sonnet 5.5 | $0.00011 | $0.00245 |
| Haiku 4.5 | $0.00005 | $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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harnss Release Workflow
Run the full release pipeline. Bump type is passed as $ARGUMENTS (major, minor, or patch).
Step 1: Pre-flight Checks
Run these commands and read every line of output:
git status
git diff --cached --stat
git diff --cached
If the diff is too large to read in one shot, read it in chunks (e.g., per-directory or line ranges). You must read the entire diff before proceeding.
Review for:
- Test files, scratch files, temp files, debug artifacts (e.g.,
test-*.ts,scratch.*,*.tmp,random-*.md) - Files that shouldn't be committed (
.env, credentials, large binaries)
If you find any:
- Unstage or remove them
- Tell the user what you removed
If there are no staged changes but unstaged changes exist, ask the user if they want to stage anything first. If the working tree is completely clean (nothing to release), tell the user and stop.
Step 2: Version Bump
Determine new version
- Read the current version from
package.json(the"version"field) - Get the latest tag:
git tag --sort=-v:refname | head -1 - Parse the current version as
MAJOR.MINOR.PATCH - Apply the bump type from
$ARGUMENTS:major→(MAJOR+1).0.0minor→MAJOR.(MINOR+1).0patch→MAJOR.MINOR.(PATCH+1)
- If
$ARGUMENTSis empty or invalid, ask the user which bump type they want
Check for SDK updates
npm view @anthropic-ai/Codex-agent-sdk version
Compare with the version in package.json under dependencies["@anthropic-ai/Codex-agent-sdk"] (strip the ^ prefix for comparison). If a newer version exists, update the dependency version (keep the ^ prefix) and tell the user.
Apply changes
- Edit
package.jsonto set the new version number - Stage it:
git add package.json - If the SDK was updated, also run:
pnpm install git add package.json pnpm-lock.yaml
Step 3: Commit
Choose the commit message based on what's staged:
Feature/fix changes staged (not just version bump)
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 · 163 lines · 54 tokens per session scan A f103688b9f3b
release is a skill published in the GitHub repository OpenSource03/harnss (392 stars, last pushed 7d ago), licensed MIT. It adds 54 tokens to every session and 1,226 once invoked, about $0.0002 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-30.
Other skills, from other repositories
publish-site
Versioned site deploys to GitHub/Cloudflare/Netlify Pages.
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
git-story-film
Direct an animated film of about two minutes from a software repository's Git history. Select real commits, releases and reverts; develop the story, character and visual style; build an outline, cast sheet, storyboard and HTML review studio; then render a 4K/60fps MP4 after approval. Use for repository or product…
changelog-generator
Convierte un git log, lista de commits o notas de lanzamiento en un changelog pulido orientado al usuario. Usa cuando estés escribiendo notas de versión, generando una entrada en CHANGELOG.md o documentando qué cambió en una versión. Produce una sección de changelog estructurada con encabezado de versión, cambios…
release-notes-from-git-log
Turn a git log into user-facing release notes grouped by feature and fix. Use when asked for release notes from this git log, a changelog entry from these commits, or to turn commits into release notes. Produces a grouped changelog with one line per change and a short headline.