Borrowing it
Nothing to install: this file belongs to swingerman/ha-dual-smart-thermostat. 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/swingerman/ha-dual-smart-thermostat/master/.claude/commands/beta-release.mdgit clone --depth 1 https://github.com/swingerman/ha-dual-smart-thermostatWrote 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/commands/swingerman/ha-dual-smart-thermostat/beta-release)<a href="https://agentmods.dev/commands/swingerman/ha-dual-smart-thermostat/beta-release"><img src="https://agentmods.dev/badge/commands/swingerman/ha-dual-smart-thermostat/beta-release/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/commands/swingerman/ha-dual-smart-thermostat/beta-release"><img src="https://agentmods.dev/badge/commands/swingerman/ha-dual-smart-thermostat/beta-release.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.00029 | $0.00564 |
| Opus 5 | $0.00015 | $0.00282 |
| Sonnet 5 | $0.00006 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
beta-release 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 10d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beta Release
Create a beta pre-release for Dual Smart Thermostat.
User Input
$ARGUMENTS
Consider the user input above (if provided) for version hints or extra release notes.
Workflow
Follow these steps in order:
1. Determine Version
- Read the current version from
custom_components/dual_smart_thermostat/manifest.json - List recent GitHub releases with
gh release list --limit 10 - Determine the next version:
- If there are already beta releases for a version higher than the latest stable release, increment the beta number (e.g.,
v0.11.3-beta1→v0.11.3-beta2) - If the manifest version matches the latest stable release, bump the patch version (e.g.,
v0.11.2→v0.11.3) unless user requests a minor bump
- If there are already beta releases for a version higher than the latest stable release, increment the beta number (e.g.,
- CRITICAL: The manifest version must NOT contain "beta" — only the clean version (e.g.,
v0.11.3), otherwise the hassfest workflow will fail
2. Bump Manifest (if needed)
If the manifest version needs to change:
- Edit
custom_components/dual_smart_thermostat/manifest.jsonto update the"version"field - Commit:
chore: bump version to vX.Y.Z - Push to master
3. Generate Release Notes
Gather commits since the last release (stable or beta) using:
git log <last-tag>..HEAD --oneline
Write concise release notes in this format:
## What's New in vX.Y.Z-betaN
Brief one-line summary of what this beta includes.
### ✨ New Features
- Feature description focusing on user value (#issue)
### 🐛 Bug Fixes
- Fix description explaining what was wrong and what's now fixed (#issue)
Rules:
- Omit sections that have no entries (e.g., skip "New Features" if there are none)
- Focus on user value, not implementation details
- Reference issue numbers where applicable
- Keep it concise — beta notes are brief
4. Create the Release
gh release create vX.Y.Z-betaN --target master --prerelease --title "vX.Y.Z-betaN" --notes "<generated notes>"
5. Report
Show the user the release URL and a summary of what was released.
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.
- 10d ago First seen · 75 lines · 29 tokens per session scan A 940608239bed
beta-release is a command published in the GitHub repository swingerman/ha-dual-smart-thermostat (233 stars, last pushed 8d ago), licensed Apache-2.0. It adds 29 tokens to every session and 564 once invoked, about $0.0001 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 commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
doc-changelog
Generation and maintenance of the project changelog.