Borrowing it
Nothing to install: this file belongs to Miraculix2050/LoxBerry-Plugin-MCP-Server. 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/Miraculix2050/LoxBerry-Plugin-MCP-Server/master/AGENTS.mdgit clone --depth 1 https://github.com/Miraculix2050/LoxBerry-Plugin-MCP-ServerWrote 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/miraculix2050/loxberry-plugin-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/miraculix2050/loxberry-plugin-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/miraculix2050/loxberry-plugin-mcp-server/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.
<a href="https://agentmods.dev/instructions/miraculix2050/loxberry-plugin-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/miraculix2050/loxberry-plugin-mcp-server/agents-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.00658 | $0.00658 |
| Opus 5 | $0.00329 | $0.00329 |
| Sonnet 5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
LoxBerry-Plugin-MCP-Server 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 8d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Instructions
This repository contains the LoxBerry MCP Server plugin. Apply the mandatory
rules below to every change. Before implementation, read only the relevant
sections of docs/development/implementation-guidelines.md: sections 3-6 for
architecture, MCP contracts, security, or configuration; section 7 for UI;
section 8 for lifecycle; section 9 for logging; and sections 10-11 for tests,
documentation, or releases. Read the whole document only for cross-cutting or
unclear changes. Select verification from
docs/development/test-strategy.md; do not reread unchanged sections during the
same task.
Working rules
- Keep changes small and compatible with the native LoxBerry plugin layout.
- Treat MCP tool names, input/output schemas, configuration keys, plugin identity, and persistent paths as contracts once released.
- Separate Loxone authorization from LoxBerry authorization. Never infer administrative LoxBerry permissions from a Loxone login.
- Default new capabilities to read-only. Mutating tools require an explicit, narrow allowlist, input validation, authorization, timeout handling, and an audit record.
- Keep developer-facing code, comments, logs, and technical diagnostics in English. Keep German and English user-facing UI and documentation synchronized.
- Never store or print credentials, tokens, session data, or private keys.
- Update documentation and tests together with behavior, configuration, permissions, dependencies, compatibility, or upgrade changes.
- Use change-driven tests. Documentation-only changes do not require device or browser acceptance unless they change generated or rendered behavior.
- During iteration use
python tools/test.py --profile changed; inspect the selection first with--planwhen scope is unclear. Reserve the Full profile for the final revision, cross-cutting fallback, CI, and release packaging. - Do not claim platform, browser, device, or Miniserver compatibility without matching evidence.
- Preserve unrelated worktree changes and inspect
git status --shortbefore committing. - Prepare release metadata and
CHANGELOG.mdthrough a reviewed PR. Official stable and prerelease packages, tags, and GitHub Releases must be created only from preparedmasterwith the owner-triggeredPublish plugin releaseworkflow. AI agents invoke that same workflow withgh workflow run; local-local-...ZIPs are test artifacts only.
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.
- 8d ago First seen · 55 lines · 658 tokens per session scan A 505dd5cd0c37
LoxBerry-Plugin-MCP-Server AGENTS.md is an instructions file published in the GitHub repository Miraculix2050/LoxBerry-Plugin-MCP-Server (1 stars, last pushed 23d ago), licensed Apache-2.0. It adds 658 tokens to every session, about $0.0033 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
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).
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.
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.