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.
git clone --depth 1 https://github.com/ckrl/ha-gitopsWrote 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/rules/ckrl/ha-gitops/hacs)<a href="https://agentmods.dev/rules/ckrl/ha-gitops/hacs"><img src="https://agentmods.dev/badge/rules/ckrl/ha-gitops/hacs/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/rules/ckrl/ha-gitops/hacs"><img src="https://agentmods.dev/badge/rules/ckrl/ha-gitops/hacs.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.00000 | $0.01100 |
| Opus 5.5 | $0.00000 | $0.00440 |
| Sonnet 5.5 | $0.00000 | $0.00220 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
hacs 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 1mo 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HACS Rules
См. docs/architecture.md §5.2–5.3 и §12.
manifest.json (custom_components/ha_gitops/manifest.json)
Обязательные поля:
{
"domain": "ha_gitops",
"name": "HA GitOps",
"version": "X.Y.Z",
"documentation": "https://github.com/<owner>/ha-gitops",
"issue_tracker": "https://github.com/<owner>/ha-gitops/issues",
"requirements": [],
"dependencies": [],
"codeowners": ["@<owner>"],
"iot_class": "cloud_polling",
"config_flow": true
}
Правила:
domainнавсегда =ha_gitops. Не менять.version— semver (MAJOR.MINOR.PATCH). Поднимать в каждом релизе. Должен совпадать с git-тегом (vX.Y.Z).requirements— пусто в MVP (зависимость наgitbinary не Python). В Release добавить"GitPython>=3.1"(точное имя пакета на PyPI).iot_class=cloud_polling— удалённый Git по SSH/сеть; в HA классификаторcloud_*отражает необходимость исходящего интернета для пользовательского UI.config_flow=true(MVP: UI Config Flow вconfig_flow.py).codeowners— массив GH-handles с@.- Brand images — каталог
custom_components/ha_gitops/brand/с минимумicon.png(квадратная иконка; см. HA brand images). Для HA 2026.3+ локальныйbrand/подхватывается API/api/brands/integration/…; HACS ожидает brand-ассеты в репозитории интеграции.
hacs.json (в корне репо)
{
"name": "HA GitOps",
"filename": "ha_gitops.zip",
"content_in_root": false,
"hide_default_branch": false,
"homeassistant": "2024.1.0"
}
content_in_root: false— компонент лежит вcustom_components/ha_gitops/.homeassistant— минимальная поддерживаемая версия HA. Поднимать только при намеренном переходе.filename— для совместимости с старыми установщиками; современный HACS это поле часто игнорирует, но оставляем.
Валидация в CI (.github/workflows/validate.yml)
Минимум обязательные шаги:
- hassfest —
home-assistant/actions/hassfest@master(валидирует manifest.json и структуру). - HACS validation —
hacs/action@mainсcategory: integration. - pytest — на матрице Python 3.11/3.12.
- Линт/формат —
ruff check,black --check.
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.
- 1mo ago First seen · 95 lines · 0 tokens per session scan A 00f34fcf984e
hacs is a cursor rule published in the GitHub repository ckrl/ha-gitops (5 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,100 tokens. 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 cursor rules, from other repositories
repository
Follow AGENTS.md and CONTRIBUTING.md before working in this repository.
python-tooling
Python tooling for the add-on source — uv, ruff, pytest, Python 3.13.
audio-streaming
Configure and receive PCM audio with Camera Stream on iOS.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.