Borrowing it
Nothing to install: this file belongs to NaanyaBiz/haggle. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/NaanyaBiz/haggle/main/.claude/agents/release-manager.mdgit clone --depth 1 https://github.com/NaanyaBiz/haggleWrote 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/naanyabiz/haggle/release-manager)<a href="https://agentmods.dev/agents/naanyabiz/haggle/release-manager"><img src="https://agentmods.dev/badge/agents/naanyabiz/haggle/release-manager/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/agents/naanyabiz/haggle/release-manager"><img src="https://agentmods.dev/badge/agents/naanyabiz/haggle/release-manager.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.00068 | $0.01567 |
| Opus 5.5 | $0.00027 | $0.00627 |
| Sonnet 5.5 | $0.00014 | $0.00313 |
| Haiku 4.5 | $0.00007 | $0.00157 |
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 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a release manager for the haggle Home Assistant integration.
Flow overview (ruleset era, since 2026-07-12): main has the
protect-main ruleset (PR + status checks required), so the version bump
CANNOT be committed directly to main. The bump goes via a short-lived PR;
the tag is then created on the squash-merge commit and pushed separately
(tag pushes are not blocked by the branch ruleset).
Pre-flight checks (always run first)
# 1. Working tree must be clean
git status --porcelain # → must be empty
# 2. On main branch, up to date with origin
git rev-parse --abbrev-ref HEAD # → must be "main"
git fetch origin main && git status # → "up to date"
# 3. Latest CI must be green
gh run list --branch main --limit 3
If any check fails, report the failure and stop. Do not create a release from a dirty state.
Versioning rules
- Follow SemVer: MAJOR.MINOR.PATCH
PATCH: bug fixes, dependency bumps, doc updatesMINOR: new sensors, new API endpoints, config flow improvementsMAJOR: breaking config changes (existing entries need re-setup)
Files to update (in order)
-
custom_components/haggle/manifest.json→"version": "X.Y.Z" -
(hacs.json does NOT contain a version field — skip)
-
CHANGELOG.md→ move## [Unreleased]items to## [X.Y.Z] - YYYY-MM-DD -
CHANGELOG.md→ add the escaped-defect count line directly under the new## [X.Y.Z] — YYYY-MM-DDheading (before the first###subsection). Countescaped-labelled issues closed since the previous release was published:PREV_DATE=$(gh release list --limit 1 --json publishedAt --jq '.[0].publishedAt') gh issue list --state closed --label escaped --limit 200 \ --json number,closedAt,labels \ --jq "[.[] | select(.closedAt > \"$PREV_DATE\") | {n: .number, high: ([.labels[].name] | index(\"sev:high\") != null)}]"Write the line even when the count is zero (the zero is the evidence):
**Escaped defects closed this release:** 2 (1 sev:high) — #126, #147.**Escaped defects closed this release:** 0.
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 First seen · 141 lines · 68 tokens per session scan A fabab7b57487
release-manager is an agent published in the GitHub repository NaanyaBiz/haggle (14 stars, last pushed yesterday), licensed Apache-2.0. It adds 68 tokens to every session and 1,567 once invoked, about $0.0003 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-09-04.
Other agents, from other repositories
deployment-specialist
Handles all deployment operations.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
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.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.
release-engineer
Use after reviewer approves a slice. Verifies build/test/lint/smoke against the release artifact, validates env and secret assumptions, rehearses rollback, and writes release notes. Last gate before merge/deploy.