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 mifunedev/openharness --skill releasegit clone --depth 1 https://github.com/mifunedev/openharnessWrote 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/mifunedev/openharness/release)<a href="https://agentmods.dev/skills/mifunedev/openharness/release"><img src="https://agentmods.dev/badge/skills/mifunedev/openharness/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/mifunedev/openharness/release"><img src="https://agentmods.dev/badge/skills/mifunedev/openharness/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.00053 | $0.01925 |
| Opus 5.5 | $0.00021 | $0.00770 |
| Sonnet 5.5 | $0.00011 | $0.00385 |
| Haiku 4.5 | $0.00005 | $0.00193 |
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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
.github/workflows/release.yml owns version allocation and artifact mutation.
The workflow validates every push to main or master first, then reserves the
v<version> tag for the version root package.json names, publishes GHCR and
the CLI (or confirms the CLI version already exists), and finally publishes the
GitHub Release. Do not pre-create a release tag, draft, or release/<version>
branch.
Root package.json holds the release version. A release is a deliberate bump:
an unchanged version gives a clean, green no-op run.
Artifact set
One release produces, from one build and one commit:
- Two npm packages:
@mifune/agro(theagroexecutable, from.oh/cli) and the@mifune/openharnessdelegation shim (theohexecutable, from.oh/cli/legacy), published in that order. The shim is deprecated toward@mifune/agroimmediately after publication. - Four immutable GHCR tags:
ghcr.io/mifunedev/openharness:<version>,:sha-<sha>,ghcr.io/mifunedev/agro:<version>, and:sha-<sha>, verified to share one manifest digest (.oh/scripts/verify-release-aliases.sh), thenlateston both repositories (.oh/scripts/promote-release-latest.sh). - Four GitHub Release assets:
agro.js,oh.js,get-agro.sh, andget-oh.sh, attached before the release is undrafted soreleases/latest/download/<asset>resolves on publication.
Version sites
A release cut bumps the same version in four places, and version-parity.sh
fails the build when they drift:
package.json(root)..oh/cli/package.jsonand.oh/cli/package-lock.json..oh/cli/legacy/package.jsonversion..oh/cli/legacy/package.jsondependencies["@mifune/agro"](exact pin, no range).
Operator prerequisites this repository cannot verify
- The npm token has publish rights for the
@mifunescope, including the@mifune/agropackage name. - The GHCR package
mifunedev/agrois set to public after its first push. A new GHCR package is private by default, soagro sandbox install dockercannot pull it until the operator changes the visibility. - The compatibility SLA clock starts at the first public AGRO release, that is,
the first release that publishes
@mifune/agroandghcr.io/mifunedev/agro.
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 Changed · +46 lines d9b0d7c70ee4
- 2mo ago First seen · 130 lines · 53 tokens per session scan A b1223f80d1e5
release is a skill published in the GitHub repository mifunedev/openharness (37 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,925 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
safety
Check secret handling, staged changes and push targets, destructive Git operations, Docker image hygiene, and new dependencies before consequential coding actions. Use for commits, pushes, container builds or publishes, dependency additions, and explicit safety reviews.
release-tag
Cut a release tag behind a real tier gate and cloud approval readback. The approval, task, approved commit, and resulting tag are bound; self-approval and HEAD drift fail closed. Prod prefixes remain refused.
git-ops
Close out a local coding task on the bound daemon — stage, commit, branch, merge, push via cloud git — and when a merge conflicts, STOP and escalate with the file list instead of auto-resolving. Push reaches only the bare replica; prod-triggering tags are refused.
release-rollback
Roll a release back for real when post-deploy regression goes red — apc release rollback flips the current version to pulled and the last good version back to current in the release ledger, and (with --mirror) repoints the bare mirror ref. Behind an approval gate; with no previous good version it BLOCKS instead of…
updater_guide
Is Row-Bot up to date? Checking for and installing Row-Bot updates.
releasing-prod
A controlled process for deploying already tested changes to the production environment. Production is the live environment used by users, and this process includes owner approval, database migration checks, deployment, and smoke tests.