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/deploy)<a href="https://agentmods.dev/skills/geniro-io/geniro-claude-harness/deploy"><img src="https://agentmods.dev/badge/skills/geniro-io/geniro-claude-harness/deploy/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/deploy"><img src="https://agentmods.dev/badge/skills/geniro-io/geniro-claude-harness/deploy.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.00032 | $0.00470 |
| Opus 5 | $0.00016 | $0.00235 |
| Sonnet 5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
deploy 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
Deploy — release pipeline
Phases overview
- Phase 0 — Preflight. Verify the working tree is clean and the tag does not exist.
- Phase 1 — Build. Produce the artifact and record its digest.
- Phase 2 — Smoke. Run the smoke suite against the built artifact.
- Phase 3 — Promote. Move the artifact into the target environment.
Loop invariants
- No promote without a green smoke run. Phase 3 reads Phase 2's result file; a missing result is a failure, never a pass.
- State writes go through the helper. Write
state.mdviaatomic_state_writefrom${CLAUDE_PLUGIN_ROOT}/lib/atomic-write.sh— a direct write truncates and rewrites, so a reader hitting that window sees a partial file.
PHASE 0 — Preflight
Confirm the tree is clean. Read the rollback contract at ${CLAUDE_PLUGIN_ROOT}/skills/_shared/rollback-contract.md before proceeding — it names what a half-promoted release leaves behind.
PHASE 1 — Build
Build the artifact. Record the digest in the state file.
PHASE 2 — Smoke
Run the smoke suite. Write the result to the state file.
PHASE 3 — Promote
Promote the artifact. When promotion fails midway, hand off to /geniro:promote for the manual completion walk.
REFERENCE
${CLAUDE_PLUGIN_ROOT}/skills/deploy/steps-reference.md— per-phase step detail${CLAUDE_PLUGIN_ROOT}/skills/deploy/SKILL.md§Phase 4 — the rollback walk, run when a promote is reverted${CLAUDE_PLUGIN_ROOT}/skills/_shared/state-write.md— state-write helper API
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.
- 8d ago First seen · 45 lines · 32 tokens per session scan A 18d950dcb7b8
deploy is a skill published in the GitHub repository geniro-io/geniro-claude-harness (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 32 tokens to every session and 470 once invoked, about $0.0002 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
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.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
updater_guide
Guidance for checking for and installing Row-Bot updates.