hacs.integration_blueprint: Skill for Claude Code

.agents/skills/blueprint-skill-maintenance/SKILL.md

blueprint-skill-maintenance is a skill for Claude Code, Codex from jpawlowski/hacs.integration_blueprint. It costs 204 tokens per session (2,578 once invoked), scanned A, original, MIT.

A guide for maintaining the set of coding-agent skills shipped with a Home Assistant integration template. A skill is a reusable set of instructions that guides an agent through a type of task.

In plain words
What is it for?
Use it when adding, updating, splitting, removing, or reviewing skills, or when updating the pinned Home Assistant version and synchronised template content.
Why use it?
It helps keep shared instructions correct, consistent, and useful across all repositories created from the template.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

This is jpawlowski/hacs.integration_blueprint's own configuration. It tells Claude Code and Codex how to work on hacs.integration_blueprint itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything hacs.integration_blueprint configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jpawlowski/hacs.integration_blueprint. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jpawlowski/hacs.integration_blueprint/main/.agents/skills/blueprint-skill-maintenance/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/jpawlowski/hacs.integration_blueprint

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for blueprint-skill-maintenance

README.md
[![agentmods](https://agentmods.dev/badge/skills/jpawlowski/hacs.integration_blueprint/blueprint-skill-maintenance/github.svg)](https://agentmods.dev/skills/jpawlowski/hacs.integration_blueprint/blueprint-skill-maintenance)
Your own site
<a href="https://agentmods.dev/skills/jpawlowski/hacs.integration_blueprint/blueprint-skill-maintenance"><img src="https://agentmods.dev/badge/skills/jpawlowski/hacs.integration_blueprint/blueprint-skill-maintenance/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.

agentmods 80×15 button for blueprint-skill-maintenance

Your own site · 80×15
<a href="https://agentmods.dev/skills/jpawlowski/hacs.integration_blueprint/blueprint-skill-maintenance"><img src="https://agentmods.dev/badge/skills/jpawlowski/hacs.integration_blueprint/blueprint-skill-maintenance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 204 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,578 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Agent Snooping · line 158
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00204 $0.02578
Opus 5 $0.00102 $0.01289
Sonnet 5 $0.00041 $0.00516
Haiku 4.5 $0.00020 $0.00258

Measured 11d ago against content hash 1736deace75b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

blueprint-skill-maintenance 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 11d 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.

.agents/skills/blueprint-skill-maintenance/SKILL.md · 165 lines

How it starts

The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Maintain the shipped skill set

This repository is the blueprint itself. Every change here reaches every integration repository generated from it, through the weekly template-sync pull request. A skill that is wrong or bloated is not one repository's problem — it is everyone's.

This skill is removed by initialize.sh when someone initialises a project from the template. Downstream maintainers get ../README.md instead, which covers writing skills for their own repository.

How to write a skill

The format, frontmatter rules, folded-scalar requirement, SYMPTOMS convention, placeholders and authoring principles are in ../README.md. Read it — this skill does not repeat it. What follows is what is specific to maintaining a set that ships to other people.

The seam: rule or procedure?

Every piece of guidance goes in exactly one place. Before writing anything into a skill, ask which of these it is:

It is… It belongs in…
A rule that holds whenever a file of that type is edited .agents/instructions/*.md
An ordered procedure, or a decision the developer has to make .agents/skills/*/SKILL.md
An explanation or rationale for whoever builds an integration docs/development/
An explanation or rationale for whoever maintains the template docs/blueprint/

The last row is decided by audience, not by subject. docs/development/CUSTOMIZATION.md describes hooks and template sync — blueprint mechanisms both — but it addresses someone who received the blueprint, so it stays there. Why the blueprint mints its development token offline addresses whoever maintains the blueprint, so it goes in docs/blueprint/DECISIONS.md.

initialize.sh deletes docs/blueprint/ wholesale, and docs/ is already in .templatesyncignore, so nothing there needs further registration. Anything blueprint-only outside that directory needs all three steps — see docs/blueprint/README.md.

Read the full file on GitHub · 165 lines

Changes

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.

  1. 11d ago First seen · 165 lines · 204 tokens per session scan A 1736deace75b

Subscribe to this mod's changes

blueprint-skill-maintenance is a skill published in the GitHub repository jpawlowski/hacs.integration_blueprint (49 stars, last pushed 4d ago), licensed MIT. It adds 204 tokens to every session and 2,578 once invoked, about $0.0010 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.

Related

Other skills, from other repositories

homeassistant

Source-layer Home Assistant guide material preserved behind the runtime guide.

ha-china/ha_claw · 15 tokens

bat-story-eval

Compare MCP tool behavior between target and baseline versions using pre-built and custom stories with diff-based triage.

homeassistant-ai/ha-mcp · 26 tokens

contrib-pr-review

Review a contribution PR for safety, quality, and readiness. Checks for security concerns, test coverage, size appropriateness, and intent alignment. Use when reviewing external contributions.

homeassistant-ai/ha-mcp · 39 tokens

bat-adhoc

Run bot acceptance tests to validate MCP tools work correctly from a real AI agent's perspective. Use when testing PRs, detecting regressions, or verifying tool changes end-to-end with Claude/Gemini CLIs.

homeassistant-ai/ha-mcp · 48 tokens

issue-to-pr-resolver

Implement a GitHub issue end-to-end — create a worktree branch, implement the feature with tests, create a draft PR, then iteratively resolve all CI failures and review comments until the PR is clean. Use when you need to fully implement a GitHub issue from start to merge-ready. Triggers on "implement issue", "resolve…

homeassistant-ai/ha-mcp · 85 tokens

my-pr-checker

Manage your own GitHub pull requests — check CI status, inline review comments, PR-level comments, resolve review threads, fix issues, and iterate until all checks pass and threads are resolved. Use for managing your own PRs (not external contributions). Triggers on "check my PR", "check PR", "/my-pr-checker ".

homeassistant-ai/ha-mcp · 75 tokens