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 skills/home-assistant/core/bump-dependencynpx skills add home-assistant/core --skill bump-dependencygit clone --depth 1 https://github.com/home-assistant/coreWrote 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/home-assistant/core/bump-dependency)<a href="https://agentmods.dev/skills/home-assistant/core/bump-dependency"><img src="https://agentmods.dev/badge/skills/home-assistant/core/bump-dependency.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.00042 | $0.01492 |
| Opus 5 | $0.00021 | $0.00746 |
| Sonnet 5 | $0.00008 | $0.00298 |
| Haiku 4.5 | $0.00004 | $0.00149 |
Grade A, and why
bump-dependency 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 3d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bump Python Package Dependency in Home Assistant Core
Follow these systematic steps to successfully bump a python package requirement in the repository, regenerate necessary derivative files, verify the integration, and raise a pull request.
Gotchas & Non-Obvious Constraints
- PR Template Integrity: Follow Home Assistant's Pull Request template (
.github/PULL_REQUEST_TEMPLATE.md) exactly as written, including any instructions inside the template itself. Preserve all sections, comments, and unchecked checkboxes unless the template explicitly says otherwise; the only allowed removal is the Breaking change section when the template instructs you to remove it if not applicable. - GitHub Tag Volatility: Release tags on GitHub are highly inconsistent (e.g.,
v1.2.3vs1.2.3vsrelease-1.2.3). Always use the automated resolverresolve_dependency.pyto check HEAD status for correct tags before hardcoding comparison URLs.
Step-by-Step Workflow Checklist
Phase A: Research and Plan
- 1. Identify Targets: Note the requested target package and target version to bump.
- 2. Discover Codebase References: Search the codebase to find all
manifest.jsonand requirements files referencing the package. - 3. Resolve Version/Tag Details: Run the integrated validation helper script to resolve version details, GitHub repo, release tag format, and formatted PR links:
uv run --no-sync python3 ./.claude/skills/bump-dependency/scripts/resolve_dependency.py <package> <old_version> [--new-version <new_version>] - 4. Plan-Validate-Execute (Draft Plan): Before modifying any files, write a brief, structured plan outlining the integrations to change, old version, new version, and the resolved comparison link. Show this draft plan to the user.
Phase B: Execute and Validate (Local Changes)
- 5. Check Uncommitted Changes: Check for any uncommitted changes in the repository. If they exist, ask the user whether to stash, commit, or discard them before proceeding.
- 6. Git Branch Setup: Create a clean branch starting from the latest
upstream/dev:git fetch upstream dev git checkout -b bump-<package>-to-<version> upstream/dev - 7. Apply Bump to manifests: Update the version constraint string in all identified
manifest.jsonfiles (e.g., change"package==1.0.0"to"package==1.1.0"). - 8. Regenerate Core Requirements: Run the requirements generator to update all derivative requirements and constraint files:
uv run --no-sync python3 -m script.gen_requirements_all - 9. Validate Requirements: Check
git diffto ensure that only the targetedmanifest.jsonfiles andrequirements_all.txt(and potentially standard constraints) were modified. No unrelated files must be affected. - 10. Local Venv Verification: Install the exact targeted package version directly inside the virtual environment:
uv pip install "<package>==<version>"
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.
- 3d ago First seen · 99 lines · 42 tokens per session scan A a65120f42e26
bump-dependency is a skill published in the GitHub repository home-assistant/core (90,198 stars, last pushed 3d ago), licensed Apache-2.0. It adds 42 tokens to every session and 1,492 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
iot-developer
Expert in IoT development, microcontrollers, sensors, and MQTT protocols.
edge-iot
Edge computing, IoT protocols, and embedded systems integration.
iot-skills
Use when developing with Raspberry Pi Pico (RP2040) for GPIO, I2C, Wi-Fi, MQTT, or sensor integration using MicroPython. Index of 1 skill: KE3036 Keyes Pico learning kit.
aether-iot-query
Use this skill when the user asks about a live AetherEdge runtime: channels, points, real-time values, history, alarms, rules, models, instances, routing, SHM health, service health, or system status. Use aether CLI commands to answer — do NOT inspect source code, local database files, or config YAMLs to answer…
aether-iot
Build, integrate, diagnose, or generate applications for the AetherEdge AI-native edge kernel. Use for AetherEdge onboarding, SDK compositions, device and topology clients, read-only operations UIs, MCP integration, Domain Packs, or governed IoT commands where live-state authority and physical-device safety must be…
devices-mcp-home
Live inventory of the user's smart home on this devices-mcp installation — cameras, Hue lights, Tapo P115 plugs, Netatmo weather, Ring, Nest Protect, Shelly sensors, and robots. Use when the user asks what devices they have, what's online, or wants a status summary before controlling hardware.