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/project-layout)<a href="https://agentmods.dev/rules/ckrl/ha-gitops/project-layout"><img src="https://agentmods.dev/badge/rules/ckrl/ha-gitops/project-layout/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/project-layout"><img src="https://agentmods.dev/badge/rules/ckrl/ha-gitops/project-layout.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.00937 | $0.00937 |
| Opus 5.5 | $0.00375 | $0.00375 |
| Sonnet 5.5 | $0.00187 | $0.00187 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
project-layout 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Layout (keep this shape)
Опорная схема — docs/architecture.md §5.1. Не меняй без обновления документа.
ha-gitops/
├── custom_components/
│ └── ha_gitops/
│ ├── __init__.py # async_setup / async_setup_entry (services) / async_unload_entry
│ ├── manifest.json # HACS manifest (domain, version, codeowners, iot_class)
│ ├── const.py # DOMAIN, CONF_*, дефолты, ключи статусов
│ ├── git_manager.py # ВСЯ git-логика; класс GitManager — единственная точка вызовов git
│ ├── sensor.py # SensorEntity: sync status + local/remote/changed/last_sync
│ ├── button.py # ButtonEntity: pull, fetch, push
│ ├── repairs.py # RepairsFlow (issue_registry fix)
│ ├── config_flow.py # UI Config Flow (MVP)
│ ├── services.yaml # описание сервисов
│ ├── strings.json # UI-строки (en по умолчанию)
│ ├── brand/ # icon.png (и при необходимости logo.png) для HA/HACS
│ └── translations/
│ └── ru.json # Russian UI (en defaults in strings.json)
├── tests/
│ ├── conftest.py # фикстуры HA + временный git repo
│ ├── test_git_manager.py # unit + integration тесты GitManager
│ ├── test_sensor.py
│ ├── test_inspection_snapshot.py
│ ├── test_ssh_keygen.py
│ ├── test_button.py
│ ├── test_config_flow.py
│ ├── test_service.py
│ ├── test_repairs.py
│ └── test_setup.py
├── docs/ # architecture.md — design of record
├── hacs.json # HACS metadata (см. hacs.mdc)
├── README.md # установка, configuration.yaml пример, prerequisites
├── LICENSE # MIT
├── pyproject.toml # dev-зависимости, pytest config, ruff/black
└── .github/workflows/
├── validate.yml # hassfest + HACS validation + pytest
└── release.yml # автотег + release notes
Ответственность модулей
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 · 62 lines · 937 tokens per session scan A 0fdbf018e973
project-layout is a cursor rule published in the GitHub repository ckrl/ha-gitops (5 stars, last pushed 5mo ago), licensed MIT. It adds 937 tokens to every session, about $0.0037 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-08-31.
Other cursor rules, from other repositories
repository
Follow AGENTS.md and CONTRIBUTING.md before working in this repository.
synced-addons
Which add-on folders are CI-synced mirrors (do not hand-edit) vs maintained here.
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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.