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.
curl -O https://raw.githubusercontent.com/jpawlowski/hacs.integration_blueprint/main/AGENTS.mdgit clone --depth 1 https://github.com/jpawlowski/hacs.integration_blueprintWrote 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/instructions/jpawlowski/hacs.integration_blueprint/agents-md)<a href="https://agentmods.dev/instructions/jpawlowski/hacs.integration_blueprint/agents-md"><img src="https://agentmods.dev/badge/instructions/jpawlowski/hacs.integration_blueprint/agents-md.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.1 | $0.07306 | $0.07306 |
| Opus 5 | $0.03653 | $0.03653 |
| Sonnet 5 | $0.01461 | $0.01461 |
| Haiku 4.5 | $0.00731 | $0.00731 |
Grade A, and why
hacs.integration_blueprint AGENTS.md 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 8d 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 — 469 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Instructions
Always-loaded project context for every AI coding agent working on this Home Assistant custom integration. Per-file style rules and task procedures live elsewhere — the routing table below says where.
Only what an agent cannot infer from the code belongs in this file. General Python, async or Home Assistant knowledge does not; this project's identity, layering, workflow policy and traps do.
Which repository is this?
initialize.sh is present, so this repository has not been initialised yet — the domain, class prefix and
directory names below are still the template's placeholders. The script replaces them across the whole repository and
then deletes itself, and template sync never restores it. Its absence, not any wording here, is what marks an
initialised integration.
Two kinds of repository are in this state, and they are byte-identical — nothing in the working tree tells them apart:
- The upstream template. The placeholders are permanent here, and the example integration is itself the thing
being maintained. Every change ships to every downstream repository through the weekly template-sync pull request,
so skills and instruction files must use the
<domain>and{ClassPrefix}placeholders rather than the concrete identifiers, andblueprint-skill-maintenancegoverns the shipped skill set. - A fresh copy made with GitHub's "Use this template" button, which still has to be initialised. Do not write
integration code first —
initialize.shwould overwrite it. Run./initialize.sh, thenblueprint-scaffold; when existing integration code is being migrated in,blueprint-importcovers the order instead.
When the request does not make clear which of the two this is, ask. Do not infer it from the git remote — a contributor's fork of the template is not a copy awaiting initialisation.
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.
- 8d ago First seen · 469 lines · 7,306 tokens per session scan A 07a3a318110e
hacs.integration_blueprint AGENTS.md is an instructions file published in the GitHub repository jpawlowski/hacs.integration_blueprint (49 stars, last pushed yesterday), licensed MIT. It adds 7,306 tokens to every session, about $0.0365 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.