Borrowing it
Nothing to install: this file belongs to kellerza/hass-addons. 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/kellerza/hass-addons/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/kellerza/hass-addonsWrote 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/kellerza/hass-addons/copilot-instructions)<a href="https://agentmods.dev/instructions/kellerza/hass-addons/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/kellerza/hass-addons/copilot-instructions/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/instructions/kellerza/hass-addons/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/kellerza/hass-addons/copilot-instructions.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.00517 | $0.00517 |
| Opus 5.5 | $0.00207 | $0.00207 |
| Sonnet 5.5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
hass-addons copilot-instructions.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 12d 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.
What it actually says
hass-addons — align with Cursor rules
This project keeps its agent and contributor policies in .cursor/rules/ as
Markdown-with-frontmatter files (*.mdc). Follow those files as the source of truth for how
to work in this repository.
What to do
- Before suggesting or applying changes in an area covered by a rule’s
globs(see the YAML frontmatter at the top of each.mdcfile), read the relevant.cursor/rules/*.mdcfile in the repo and obey its body (the markdown after the closing---of the frontmatter block). - Repository-wide / always-on rules: if a rule sets
alwaysApply: truein its frontmatter, treat it as binding for all work in this repo unless the user explicitly overrides it in the current conversation. - When new rules are added under
.cursor/rules/, use them the same way: prefer the rule text over assumptions from similar projects.
Current rule files (index)
| Path | Typical scope | Topic |
|---|---|---|
.cursor/rules/kiss-ponytail.mdc |
Always on | Lazy senior dev mode: pick the simplest solution that works; reuse before writing; root-cause bug fixes; one runnable check for non-trivial logic. |
.cursor/rules/synced-addons.mdc |
Always on | Which add-on folders are CI-synced mirrors (hass-addon-sunsynk-edge/, hass-addon-sunsynk-multi/, hass-addon-mbusd/, hass-addon-sma-em-edge/) and must not be hand-edited, vs the add-ons maintained here; packaging-vs-behaviour split. |
.cursor/rules/python-tooling.mdc |
src/**/*.py, pyproject.toml |
Python 3.13, uv, ruff, pytest conventions for the add-on source packages. |
If this index drifts, trust the .mdc files; update this table when you add or rename rules.
Conflicts
If another document in the repo disagrees with a .cursor/rules/*.mdc rule,
follow the .mdc rule unless the user or maintainer explicitly says otherwise in the current
thread.
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.
- 12d ago First seen · 33 lines · 517 tokens per session scan A 2a24b774f36a
hass-addons copilot-instructions.md is an instructions file published in the GitHub repository kellerza/hass-addons (9 stars, last pushed 3d ago), licensed Apache-2.0. It adds 517 tokens to every session, about $0.0021 per session on Opus 5.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-10-02.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.