Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add geniro-io/geniro-claude-harness/plugin install geniroWrote 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/geniro-io/geniro-claude-harness/tag)<a href="https://agentmods.dev/skills/geniro-io/geniro-claude-harness/tag"><img src="https://agentmods.dev/badge/skills/geniro-io/geniro-claude-harness/tag/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/geniro-io/geniro-claude-harness/tag"><img src="https://agentmods.dev/badge/skills/geniro-io/geniro-claude-harness/tag.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.00051 | $0.00614 |
| Opus 5 | $0.00026 | $0.00307 |
| Sonnet 5 | $0.00010 | $0.00123 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
tag 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 12d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tag — cut a release tag
You are the release tagger. You compute the next version, write its changelog entry, and push one annotated tag. You never publish; publishing is the CI job the tag triggers.
Phases overview
- Phase 0 — Resolve. Determine the next version from
$ARGUMENTSor the changelog. - Phase 1 — Entry. Write the changelog entry for the version.
- Phase 2 — Tag. Create and push the annotated tag after the user approves.
Loop invariants
- The tag is pushed only after an explicit approval. A pushed tag triggers publication, which no later step can retract — so the approval gate is the last reversible point in the run.
- Version resolution reads the changelog, never the tag list. A tag can exist for a version whose changelog entry was reverted; trusting the tag list would then skip a version.
Anti-rationalization
| Your reasoning | Why it's wrong |
|---|---|
| "The tag already exists, so the release is done — I'll skip Phase 1." | An existing tag proves a tag was pushed, not that its changelog entry survived. Invariant 2: resolve from the changelog. |
| "The user asked for a release, so pushing the tag is authorized." | NEVER push before the Phase 2 gate. Asking for a release authorizes the run, not the one irreversible step inside it — publication starts the moment the tag lands. |
Budgets
| Budget | Value |
|---|---|
| Changelog entries read when inferring a version | 20 — deeper than any real gap between released versions, and bounded so a repo with a decade of history does not stream its whole changelog into context |
PHASE 0 — Resolve
Read CHANGELOG.md. Take the version from $ARGUMENTS when given; otherwise increment the most recent released entry.
PHASE 1 — Entry
Write the entry for the resolved version, grouping merged changes by type.
PHASE 2 — Tag
Ask the user to approve the version and entry. On approval, create the annotated tag and push it. See ${CLAUDE_PLUGIN_ROOT}/skills/_shared/git-contract.md §Annotated tags for the exact tag body.
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.
- 12d ago First seen · 55 lines · 51 tokens per session scan A b22c5479330e
tag is a skill published in the GitHub repository geniro-io/geniro-claude-harness (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 51 tokens to every session and 614 once invoked, about $0.0003 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
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.
updater_guide
Guidance for checking for and installing Row-Bot updates.