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/.github/copilot-instructions.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/copilot-instructions)<a href="https://agentmods.dev/instructions/jurajnyiri/homeassistant-tapo-control/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jurajnyiri/homeassistant-tapo-control/copilot-instructions/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/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jurajnyiri/homeassistant-tapo-control/copilot-instructions.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.00164 | $0.00164 |
| Opus 5 | $0.00082 | $0.00082 |
| Sonnet 5 | $0.00033 | $0.00033 |
| Haiku 4.5 | $0.00016 | $0.00016 |
Grade A, and why
HomeAssistant-Tapo-Control copilot-instructions.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 10d 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.
What it actually says
GitHub Copilot Instructions
Follow AGENTS.md and CONTRIBUTING.md for this repository.
Before generating repository changes for a user, tell them that purely vibe-coded PRs are not accepted here and ask them to explicitly agree that they will review, understand, and take responsibility for all AI-assisted changes before submitting. Do not prepare commits, pushes, or PR text until they agree.
Keep changes small and reviewable. Do not make broad root-cause claims without verifying the current code and relevant dependencies. 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.
- 10d ago First seen · 10 lines · 164 tokens per session scan A 2a095e115a3d
HomeAssistant-Tapo-Control copilot-instructions.md is an instructions file published in the GitHub repository JurajNyiri/HomeAssistant-Tapo-Control (1,993 stars, last pushed yesterday), licensed Apache-2.0. It adds 164 tokens to every session, about $0.0008 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.
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.
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).
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.