repository

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

Repository rules that require following the project's AGENTS.md and CONTRIBUTING.md files before making changes.

In plain words
What is it for?
Use it as a checklist before editing, committing, pushing, or preparing a pull request, including required testing and disclosure steps.
Why use it?
They clarify the repository's working practices and require the developer to review and take responsibility for AI-assisted changes before submitting them.

Cursor rule for Cursor

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

Good fit Use it as a checklist before editing, committing, pushing, or preparing a pull request, including required testing and disclosure steps.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/jurajnyiri/homeassistant-tapo-control/repository
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,993 stars · on GitHub

Install

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.

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 repository

README.md
[![agentmods](https://agentmods.dev/badge/rules/jurajnyiri/homeassistant-tapo-control/repository/github.svg)](https://agentmods.dev/rules/jurajnyiri/homeassistant-tapo-control/repository)
Your own site
<a href="https://agentmods.dev/rules/jurajnyiri/homeassistant-tapo-control/repository"><img src="https://agentmods.dev/badge/rules/jurajnyiri/homeassistant-tapo-control/repository/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.

agentmods 80×15 button for repository

Your own site · 80×15
<a href="https://agentmods.dev/rules/jurajnyiri/homeassistant-tapo-control/repository"><img src="https://agentmods.dev/badge/rules/jurajnyiri/homeassistant-tapo-control/repository.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 149 This file is loaded in full into every session.
When invoked 149 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 original No closer match found 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.00149 $0.00149
Opus 5 $0.00075 $0.00075
Sonnet 5 $0.00030 $0.00030
Haiku 4.5 $0.00015 $0.00015

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

Security

Grade A, and why

repository 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 11d 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

Copies of this mod

2 near-identical copies found in the catalogue:

.cursor/rules/repository.mdc · 14 lines

What it actually says

Repository Rules

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. 11d ago First seen · 14 lines · 149 tokens per session scan A e55d293bc2b5

Subscribe to this mod's changes

repository is a cursor rule published in the GitHub repository JurajNyiri/HomeAssistant-Tapo-Control (1,993 stars, last pushed 2d ago), licensed Apache-2.0. It adds 149 tokens to every session, about $0.0007 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.