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/naanyabiz/haggle/release-managergit 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.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 | $0.00068 | $0.01567 |
| Opus 5 | $0.00034 | $0.00783 |
| Sonnet 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 today.
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.
- today First seen · 141 lines · 68 tokens per session scan A fabab7b57487
release-manager is an agent published in the GitHub repository NaanyaBiz/haggle (13 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. 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
aemo-mcp-expert
Use when the user asks about Australian electricity market data — spot prices, generation, demand, interconnector flows, rooftop solar, predispatch forecasts. Translates plain-English questions into aemo-mcp tool calls. NEM only (NSW1/QLD1/SA1/TAS1/VIC1); Western Australia WEM is out of scope.
development
Read this document when setting up the repository, running the server, choosing verification commands, researching Home Assistant APIs, or orienting yourself in the architecture. Behavioral rules about when testing is required remain in AGENTS.md; test implementation details live in tests/AGENTS.md.
custom-component
Read this document before changing customcomponents/hamcptools/ or a server feature that depends on the component. The HACS component and the ha-mcp server ship through separate installation paths, so compatibility must hold in both update directions.
home-assistant-apps
Read this document before changing the stable or development Home Assistant app configuration, publishing behavior, or webhook-proxy app. General release automation is documented in GitHub workflow reference.
blocky-bump-review
The concrete definition of what CLAUDE.md calls the manual review a Blocky bump requires. Renovate opens these as a one-line change to BLOCKYVERSION in blocky/Dockerfile (Tempio bumps are the same shape via TEMPIOVERSION). Most bumps merge as that bare one-liner — this runbook is how you earn that conclusion instead…
ha-esphome-config-reviewer
Produces one bundled, read-only device-level review of an ESPHome device configuration: config-pattern conformance, credential and API/OTA hardening, schema currency against the official ESPHome docs, Home-Assistant-driven binding correctness, display rendering discipline, display design conformance (palette roles…