HomeAssistant-Tapo-Control: Cursor rule for Cursor

.cursorrules

cursorrules is a cursor rule for Cursor from JurajNyiri/HomeAssistant-Tapo-Control. It costs 132 tokens per session, scanned A, a copy of repository, Apache-2.0.

Repository rules for coding agents working on a project. They require following the project's AGENTS.md and CONTRIBUTING.md files and getting the user's agreement before making changes.

In plain words
What is it for?
Use them before editing files, creating commits, pushing branches, or preparing pull requests, especially for Home Assistant behavior changes.
Why use it?
They ensure changes are focused, reviewed by a human, tested, and consistent with the project's contribution process.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/. Also seen: mentions AGENTS.md.

This is JurajNyiri/HomeAssistant-Tapo-Control's own configuration. It tells Cursor how to work on HomeAssistant-Tapo-Control 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 HomeAssistant-Tapo-Control configures →

About the project

JurajNyiri/HomeAssistant-Tapo-Control is a custom Home Assistant component that adds Tapo cameras, doorbells, and chimes to the home-automation system. It lets Home Assistant users control these devices and access streams, including for some devices without RTSP or ONVIF support. Catalogue add-ons support coding-agent work on this component.

JurajNyiri/HomeAssistant-Tapo-Control · 1,992 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to JurajNyiri/HomeAssistant-Tapo-Control. 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/JurajNyiri/HomeAssistant-Tapo-Control/main/.cursorrules
Clone the repo
git clone --depth 1 https://github.com/JurajNyiri/HomeAssistant-Tapo-Control

Made for: Cursor.

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 cursorrules

README.md
[![agentmods](https://agentmods.dev/badge/rules/jurajnyiri/homeassistant-tapo-control/cursorrules.svg)](https://agentmods.dev/rules/jurajnyiri/homeassistant-tapo-control/cursorrules)
Your own site
<a href="https://agentmods.dev/rules/jurajnyiri/homeassistant-tapo-control/cursorrules"><img src="https://agentmods.dev/badge/rules/jurajnyiri/homeassistant-tapo-control/cursorrules.svg" alt="Measured on agentmods" height="20"></a>
Per session 132 This file is loaded in full into every session.
When invoked 132 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 92% copy Near-identical to another mod 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.00132 $0.00132
Opus 5 $0.00066 $0.00066
Sonnet 5 $0.00026 $0.00026
Haiku 4.5 $0.00013 $0.00013

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

Security

Grade A, and why

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

Origin

This is a copy

92% identical to repository — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursorrules · 8 lines

What it actually says

Follow AGENTS.md and CONTRIBUTING.md before working in this repository.

Do not edit files, create commits, push branches, or prepare PRs until the user explicitly agrees that purely vibe-coded PRs are not accepted and that they will review, understand, and take responsibility for all AI-assisted changes before submitting.

Keep changes small, focused, verified, and easy to review. Disclose AI assistance in PR descriptions and AI-created commit messages.

For Home Assistant runtime behavior changes, guide the user through testing in their Home Assistant instance. Ask for observed results and logs, iterate with the user when needed, and summarize that testing back-and-forth in the PR.

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. 8d ago First seen · 8 lines · 132 tokens per session scan A a815d8092256

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository JurajNyiri/HomeAssistant-Tapo-Control (1,992 stars, last pushed 3d ago), licensed Apache-2.0. It adds 132 tokens to every session, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to repository, differing in 8 lines, and is treated as a copy.