Borrowing it
Nothing to install: this file belongs to ikari-software/fibaro-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.
curl -O https://raw.githubusercontent.com/ikari-software/fibaro-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/ikari-software/fibaro-mcpWrote 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/ikari-software/fibaro-mcp/claude-md)<a href="https://agentmods.dev/instructions/ikari-software/fibaro-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ikari-software/fibaro-mcp/claude-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.1 | $0.00882 | $0.00882 |
| Opus 5 | $0.00441 | $0.00441 |
| Sonnet 5 | $0.00176 | $0.00176 |
| Haiku 4.5 | $0.00088 | $0.00088 |
Grade A, and why
fibaro-mcp CLAUDE.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 6d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fibaro MCP Server - AI Assistant Guidelines
This file provides instructions for AI assistants (like Claude) when using the Fibaro MCP tools.
Critical: Avoid Large List Operations
NEVER start by listing all devices, scenes, or rooms without filters. These operations can return over 1MB of data and waste context window.
Bad Patterns (Avoid)
fibaro_device operation=list # Lists ALL devices - can be 1MB+
fibaro_scene operation=list # Lists ALL scenes
fibaro://devices # Resource with all device states
Good Patterns (Use These)
# Get specific device by name
fibaro_device operation=get name="Kitchen Light"
# Filter devices by room
fibaro_device operation=list room_id=5
# Get specific scene
fibaro_scene operation=get name="Good Night"
# Use analytics for overview
fibaro_analytics operation=system_health
fibaro_analytics operation=dashboard
Name-Based Lookups
All tools support looking up items by name - you rarely need IDs:
# Control device by name
fibaro_device operation=control name="Living Room Lamp" action=turnOn
# Run scene by name
fibaro_scene operation=run name="Morning Routine"
# Get variable by name
fibaro_variable operation=get name=HomeMode
Efficient Information Gathering
- For system overview: Use
fibaro_analytics operation=dashboard - For health check: Use
fibaro_analytics operation=system_health - For specific device: Use
fibaro_device operation=get name="..." - For room devices: Use
fibaro_device operation=list room_id=X
Getting Energy/Power Data
For aggregated power consumption:
# Historical power/energy data from HC2 summary-graph API (RECOMMENDED)
# For devices:
fibaro_home op=energy_graph from=1767943794 to=1767947394 device_id=955
fibaro_home op=energy_graph from=1767943794 to=1767947394 device_id=955 property=energy
# For rooms:
fibaro_home op=energy_graph from=1767943794 to=1767947394 grouping=rooms room_id=226
# Device stats with auto-aggregation
fibaro_home op=device_stats device_id=42 from=1704067200 to=1704153600
# Energy trends analysis (by room, device type)
fibaro_analytics operation=energy_trends days=7
# For a specific room's energy
fibaro_analytics operation=energy_trends days=7 room_id=5
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.
- 6d ago First seen · 110 lines · 882 tokens per session scan A ca59f5b0e491
fibaro-mcp CLAUDE.md is an instructions file published in the GitHub repository ikari-software/fibaro-mcp (2 stars, last pushed 6mo ago), licensed MIT. It adds 882 tokens to every session, about $0.0044 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-31.
Other instructions, from other repositories
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).
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.
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).
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.