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.
npx agentmods add instructions/funfr/ha-indygo-pool/agents-mdgit clone --depth 1 https://github.com/FunFR/ha-indygo-poolWrote 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/funfr/ha-indygo-pool/agents-md)<a href="https://agentmods.dev/instructions/funfr/ha-indygo-pool/agents-md"><img src="https://agentmods.dev/badge/instructions/funfr/ha-indygo-pool/agents-md.svg" alt="Measured on agentmods" 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 | $0.00932 | $0.00932 |
| Opus 5 | $0.00466 | $0.00466 |
| Sonnet 5 | $0.00186 | $0.00186 |
| Haiku 4.5 | $0.00093 | $0.00093 |
Grade A, and why
ha-indygo-pool AGENTS.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 4d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file serves as a guide for AI agents working on the ha-indygo-pool project. Follow these instructions to ensure consistency, quality, and maintainability.
🧠 Philosophy & Principles
- KISS (Keep It Simple, Stupid): Avoid over-engineering. Solutions should be simple and easy to understand.
- DRY (Don't Repeat Yourself): Reuse code where possible. Extract common logic into helper functions or classes.
- Modern Home Assistant Architecture: Follow the latest Home Assistant Developer Docs. Use
DataUpdateCoordinatorfor polling, config flows for setup, and standard entity platforms.- HTTP Requests: ALWAYS use
homeassistant.helpers.aiohttp_client.async_create_clientsessionorasync_get_clientsessioninstead of instantiatingaiohttp.ClientSessiondirectly. - Entity Translations: Use
translation_keyin entity descriptions. DO NOT hardcode English strings in thenameattribute of EntityDescriptions if a translation key is present. - Constants: Use native HA constants (e.g.,
UnitOfTime.HOURS) instead of hardcoded strings whenever possible.
- HTTP Requests: ALWAYS use
- Test-Driven Mental Model: Always verify changes. If you break it, you buy it.
📂 Project Structure & Responsibilities
api.py: Contains ALL core logic for interacting with the MyIndygo API. No Home Assistant code here.coordinator.py: Handles data fetching and caching usingDataUpdateCoordinator. Maps API data to a format usable by entities.entity.py: Base entity class to shareCoordinatorEntitylogic anddevice_infoacross all platforms.sensor.py/binary_sensor.py: Entity platform definitions. Should be thin wrappers around data from the coordinator.config_flow.py: Handles integration setup and option flows.diagnostics.py: Generates diagnostic data for easier troubleshooting.strings.json: Contains ALL user-facing strings (labels, descriptions, errors). NEVER hardcode strings in Python files.tests/: Containspytesttests. Mirror the source structure.
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.
- 4d ago First seen · 44 lines · 932 tokens per session scan A 3e5da91672b5
ha-indygo-pool AGENTS.md is an instructions file published in the GitHub repository FunFR/ha-indygo-pool (11 stars, last pushed 5d ago), licensed Apache-2.0. It adds 932 tokens to every session, about $0.0047 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
ha-mcp AGENTS.md
AGENTS.md instructions for homeassistant-ai/ha-mcp, covering agents.md, instruction structure, repository structure, worktree workflow and project overview.
ha-selora-ai CLAUDE.md
Claude Code instructions for SeloraHomes/ha-selora-ai, covering selora ai — home assistant integration, what this is, architecture, project structure and key conventions.
ecowitt_local CLAUDE.md
Claude Code instructions for alexlenk/ecowitt_local, covering claude.md, project overview, ⚠️ critical: entity creation pipeline issues, development commands and local environment.
hacs.integration_blueprint AGENTS.md
Instructions for jpawlowski/hacs.integration_blueprint, covering ai agent instructions, which repository is this?, project overview, where the rules live and routing table.
OVO_Aus_api AGENTS.md
Instructions for HallyAus/OVO_Aus_api, covering ovo energy australia (ha integration) — agent brief, what a mistake costs, stack, run it and where things live.
hass-mcp-server AGENTS.md
AGENTS.md instructions for ganhammar/hass-mcp-server, covering working on this integration, calling into home assistant, before replacing a private call with a service, anything left in category 2 or 3 and conventions.