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/huber/fronius-mcp-server/claude-mdgit clone --depth 1 https://github.com/huber/fronius-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/huber/fronius-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/huber/fronius-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/huber/fronius-mcp-server/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.02083 | $0.02083 |
| Opus 5 | $0.01042 | $0.01042 |
| Sonnet 5 | $0.00417 | $0.00417 |
| Haiku 4.5 | $0.00208 | $0.00208 |
Grade A, and why
fronius-mcp-server 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 5d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Development Commands
- Development mode:
npm run dev(uses tsx with hot reload) - Build:
npm run build(compiles TypeScript to dist/) - Start production:
npm start(runs compiled JavaScript) - Install dependencies:
npm install - Lint:
npm run lint(ESLint 9.x with flat config) - Type check:
npm run typecheck(TypeScript compiler check) - Test connection:
npm run test-connection(full API connectivity test) - Docker build:
npm run docker:build(build Docker image locally) - Docker compose:
docker-compose up -d(run with docker-compose)
Architecture Overview
This is a TypeScript-based Model Context Protocol (MCP) server that provides comprehensive access to Fronius solar inverter data. The application uses a modular architecture with proper separation of concerns and is designed for Claude Desktop integration.
Project Structure
src/
├── types/ # TypeScript type definitions
│ ├── fronius.ts # Complete Fronius API response types
│ └── config.ts # Configuration interfaces
├── services/ # Business logic services
│ ├── fronius-api.ts # Full Fronius API client with retry logic
│ └── config.ts # Configuration management and validation
├── handlers/ # MCP protocol handlers
│ ├── resources.ts # Resource-based data access
│ └── tools.ts # Tool-based interactive access
├── utils/ # Utility functions
│ └── version.ts # Centralized version management
└── server.ts # Main server with error handling and lifecycle
Core Components
FroniusAPIClient (src/services/fronius-api.ts)
- Complete TypeScript implementation of Fronius Solar API v1
- Supports all major endpoints including GetStorageRealtimeData and GetOhmPilotRealtimeData
- No fallback values - proper error handling so LLM understands failures
- Configurable timeouts, retry counts, and connection parameters
- Built-in connection testing and health checks
- Uses centralized User-Agent from version utility
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.
- 5d ago First seen · 208 lines · 2,083 tokens per session scan A 29601a1d8ba6
fronius-mcp-server CLAUDE.md is an instructions file published in the GitHub repository huber/fronius-mcp-server (4 stars, last pushed 9mo ago), licensed MIT. It adds 2,083 tokens to every session, about $0.0104 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
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.
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 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.