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.
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.
curl -O https://raw.githubusercontent.com/JurajNyiri/HomeAssistant-Tapo-Control/main/GEMINI.mdgit clone --depth 1 https://github.com/JurajNyiri/HomeAssistant-Tapo-ControlWrote 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/jurajnyiri/homeassistant-tapo-control/gemini-md)<a href="https://agentmods.dev/instructions/jurajnyiri/homeassistant-tapo-control/gemini-md"><img src="https://agentmods.dev/badge/instructions/jurajnyiri/homeassistant-tapo-control/gemini-md/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/jurajnyiri/homeassistant-tapo-control/gemini-md"><img src="https://agentmods.dev/badge/instructions/jurajnyiri/homeassistant-tapo-control/gemini-md.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.00143 | $0.00143 |
| Opus 5 | $0.00072 | $0.00072 |
| Sonnet 5 | $0.00029 | $0.00029 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
HomeAssistant-Tapo-Control GEMINI.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 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.
This is a copy
94% identical to HomeAssistant-Tapo-Control CLAUDE.md — 2 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.
What it actually says
Gemini Instructions
Follow AGENTS.md and CONTRIBUTING.md before working in this repository.
You must 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.
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.
- 11d ago First seen · 10 lines · 143 tokens per session scan A 0f521da36986
HomeAssistant-Tapo-Control GEMINI.md is an instructions file published in the GitHub repository JurajNyiri/HomeAssistant-Tapo-Control (1,993 stars, last pushed 2d ago), licensed Apache-2.0. It adds 143 tokens to every session, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to HomeAssistant-Tapo-Control CLAUDE.md, differing in 2 lines, and is treated as a copy.
Other instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).