Use it as a reference when changing the server, its lighting tools, API client, data models, or authentication code.

It gives an agent the project-specific rules needed to work consistently in that codebase.

How oWretch/zencontrol-cloud-mcp configures Codex and OpenCode

Q: What is zencontrol-cloud-mcp AGENTS.md?

An AGENTS.md instruction file for the ZenControl Cloud MCP server, which lets AI assistants control ZenControl DALI-2 lighting systems. It documents the project’s Python version, libraries, folders, and naming rules.

Reuse

Borrowing it

Nothing to install: this file belongs to oWretch/zencontrol-cloud-mcp. 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/oWretch/zencontrol-cloud-mcp/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/oWretch/zencontrol-cloud-mcp

Made for: Codex, OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/owretch/zencontrol-cloud-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/owretch/zencontrol-cloud-mcp/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/owretch/zencontrol-cloud-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/owretch/zencontrol-cloud-mcp/agents-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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/owretch/zencontrol-cloud-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/owretch/zencontrol-cloud-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,081 This file is loaded in full into every session.

When invoked 1,081 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.

Model	Per session	Once invoked
Fable 5.1	$0.01081	$0.01081
Opus 5.5	$0.00432	$0.00432
Sonnet 5.5	$0.00216	$0.00216
Haiku 4.5	$0.00108	$0.00108

Measured 2mo ago against content hash 9624a331b1a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

zencontrol-cloud-mcp 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 2mo 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.

AGENTS.md · 119 lines

How it starts

The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Instructions — zencontrol-cloud-mcp

This is an MCP (Model Context Protocol) server that lets AI assistants control ZenControl DALI-2 lighting systems. Keep these conventions in mind when working on the codebase.

Language & Runtime

Python 3.11+, async-first (async def everywhere, httpx.AsyncClient).
Package manager: uv. Run tools with uv run.
Entry point: src/zencontrol_cloud_mcp/server.py → main().

Key Libraries

Library	Purpose
`fastmcp`	MCP server framework (tools, lifespan, transports)
`httpx`	Async HTTP client for ZenControl Cloud REST API
`pydantic`	Data models / schemas for all API types
`cryptography`	Fernet encryption for stored OAuth tokens
`platformdirs`	Cross-platform token storage paths

File Organisation

src/zencontrol_cloud_mcp/
  server.py        — FastMCP server, lifespan, CLI
  tools/           — MCP tool definitions (one file per domain)
  api/             — HTTP client (client.py) and domain methods (rest.py)
  models/          — Pydantic schemas (schemas.py)
  auth/            — OAuth flow, token storage, proxy server

Naming Conventions

Functions / tools: snake_case (e.g., list_sites, control_light).
Pydantic models: PascalCase (e.g., SiteDetails, GroupSummary).
Files: snake_case.py, one module per logical domain.

Tool Design Patterns

Scope-parameterised tools

Tools that list entities (groups, devices) accept scope_type and scope_id instead of having separate tools per scope. Example:

@mcp.tool()
async def list_groups(
    ctx: Context,
    scope_type: Literal["site", "floor", "map", "gateway"],
    scope_id: str,
) -> str: ...

Accessing the API

All tools get the API client from the MCP lifespan context:

api: ZenControlAPI = ctx.lifespan_context["api"]

Never construct ZenControlAPI or ZenControlClient inside a tool.

Return values

Tools return formatted strings (not raw JSON), because the output is consumed by an LLM. Use bullet lists, tables, or short paragraphs.

Read the full file on GitHub · 119 lines

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.

2mo ago First seen · 119 lines · 1,081 tokens per session scan A 9624a331b1a2

Subscribe to this mod's changes

zencontrol-cloud-mcp AGENTS.md is an instructions file published in the GitHub repository oWretch/zencontrol-cloud-mcp (0 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 1,081 tokens to every session, about $0.0043 per session on Opus 5.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-31.

Hardware and IoT

zencontrol-cloud-mcp AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
zencontrol-cloud-mcp AGENTS.mdoWretch/zencontrol-cloud-mcp	Instructions file	0	3mo ago	Apache-2.0	A	1,081	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,649	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

zencontrol-cloud-mcp: Instructions file for Codex