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 Cantara/kcp-harness --skill cut-a-releasegit clone --depth 1 https://github.com/Cantara/kcp-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/cantara/kcp-harness/cut-a-release)<a href="https://agentmods.dev/skills/cantara/kcp-harness/cut-a-release"><img src="https://agentmods.dev/badge/skills/cantara/kcp-harness/cut-a-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/cantara/kcp-harness/cut-a-release"><img src="https://agentmods.dev/badge/skills/cantara/kcp-harness/cut-a-release.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00496 |
| Opus 5 | $0.00000 | $0.00248 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
cut-a-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 9d 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
Cut a release
Governed skill: cut a kcp-harness release through its two-workflow handoff without skipping a step or double-tagging.
Preconditions
mainis green (CI passing) at the commit you intend to release.- You know the target version (semver) and it is NOT already tagged
(
git ls-remote --tags originto check).
Steps
- (edit) Bump
versioninpackage.jsonon achore(release): vX.Y.Zcommit merged tomainfirst.release.ymldoes not do this for you, andci.yml's publish step ships whateverpackage.jsonsays at publish time. - (bash) Trigger
release.ymlviagh workflow run release.yml -f version=vX.Y.Z -f target=main(or the Actions UI). This one workflow tags, cross-compiles native binaries for 5 targets, smoke-tests linux-x64, creates the GitHub release with binaries +SHA256SUMS.txtattached, and — as its LAST step — dispatchesci.ymlonmainfor npm publish. Do not tag manually first: the workflow checks for an existing tag and no-ops the tag step if one is already pushed, but a hand-pushed tag just adds a race with no benefit. - (read) Watch the
releaserun to completion, then confirmci.yml'spublishjob (triggered by that hand-off, not by the tag push) went green.
Verification
npm view kcp-harness version equals the tag you cut, the GitHub release has 5 binaries plus
SHA256SUMS.txt, and the ci.yml publish job dispatched by release.yml is green.
Rollback
If the tag/release built but npm publish failed: fix forward, do not delete or move the pushed
tag — re-run ci.yml via workflow_dispatch once the issue is fixed. If step 1 was skipped
(version not bumped): npm publish --provenance will fail as a duplicate version — bump
package.json, commit to main, and re-dispatch ci.yml.
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.
- 9d ago First seen · 34 lines · 0 tokens per session scan A 2a2906197eb3
cut-a-release is a skill published in the GitHub repository Cantara/kcp-harness (0 stars, last pushed 15d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 496 tokens. 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.