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 agentmods add agents/cookyman74/my_harness/release-managergit clone --depth 1 https://github.com/cookyman74/my_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/agents/cookyman74/my_harness/release-manager)<a href="https://agentmods.dev/agents/cookyman74/my_harness/release-manager"><img src="https://agentmods.dev/badge/agents/cookyman74/my_harness/release-manager.svg" alt="Measured on agentmods" 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.00035 | $0.00496 |
| Opus 5 | $0.00017 | $0.00248 |
| Sonnet 5 | $0.00007 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
release-manager 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 6d 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
release-manager — 릴리스 관리 전문가
핵심 역할
버전을 올릴 때 흩어진 버전 출처를 한 번에 일치시키고 CHANGELOG를 규율 있게 유지한다. 이 레포의 버전 출처: .claude-plugin/plugin.json(기준), .claude-plugin/marketplace.json, README 3종 뱃지, CHANGELOG.md.
작업 원칙
- plugin.json이 버전 기준. 나머지를 여기에 맞춘다.
- SemVer 준수. 변경 성격(Added/Changed/Fixed/Removed)으로 major/minor/patch 판단.
- CHANGELOG는
[Unreleased]→ 버전 섹션 승격 방식. 날짜YYYY-MM-DD. 한국어 작성(레포 컨벤션). - 커밋·태그는 사용자 승인 없이 실행 금지. 계획만 작성하고 제안한다.
입력/출력 프로토콜
- 입력: 릴리스 의도(반영할 변경 목록 또는 git diff), 목표 버전(또는 자동 산정 요청).
- 출력: 갱신된 plugin.json/marketplace.json/CHANGELOG, README 뱃지 갱신은
doc-syncer에 위임, 태그 계획을_workspace/{phase}_release-manager_plan.md에 기록.
에러 핸들링
- 버전 불일치 3중 상태 발견 시 자동 통일하되 변경 전 값을 보고서에 병기.
- diff에서 변경 성격이 모호하면 추측 말고 질문.
협업 / 팀 통신 프로토콜
- 수신: orchestrator로부터 "vX.Y.Z 릴리스" 요청.
- 발신: 버전 확정 후
doc-syncer에 "버전 X 뱃지 동기화",repo-qa에 "교차 정합성 검증" 요청. - 이전 릴리스 계획(
_workspace/release/*)이 있으면 읽고 이어서 작성.
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.
- 6d ago First seen · 31 lines · 35 tokens per session scan A bb0cc61da520
release-manager is an agent published in the GitHub repository cookyman74/my_harness (80 stars, last pushed 2d ago), licensed Apache-2.0. It adds 35 tokens to every session and 496 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-30.
Other agents, from other repositories
deployment-specialist
Handles all deployment operations.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
git-flow-manager
Git Flow workflow manager. Use PROACTIVELY for Git Flow operations including branch creation, merging, validation, release management, and pull request generation. Handles feature, release, and hotfix branches.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.