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/idoru/influxdb-mcp-server/claude-mdgit clone --depth 1 https://github.com/idoru/influxdb-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/idoru/influxdb-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/idoru/influxdb-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/idoru/influxdb-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.00499 | $0.00499 |
| Opus 5 | $0.00249 | $0.00249 |
| Sonnet 5 | $0.00100 | $0.00100 |
| Haiku 4.5 | $0.00050 | $0.00050 |
Grade A, and why
influxdb-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 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.
What it actually says
InfluxDB MCP Server - Guide for Claude
Build & Test Commands
- Run all tests:
npm test - Run a single test:
npm test -- -t "test name"(e.g.,npm test -- -t "should list organizations") - Skip integration tests:
npm test -- --testPathIgnorePatterns=integration.test.js - Install dependencies:
npm install - Start server:
INFLUXDB_TOKEN=your_token node src/index.js - Test with Docker: Make sure Docker is running before executing tests
- Debug tests: Add
DEBUG=mcp:*environment variable for detailed MCP protocol logging
Code Style Guidelines
- Language: ES Modules JavaScript with TypeScript types (file extensions: .js)
- Testing: Jest with 60-second timeout for Docker operations
- Formatting: 2-space indentation
- Naming: camelCase for variables/functions, PascalCase for classes
- Types: Zod for runtime type validation
- Error handling: Try/catch blocks with structured error messages
- Imports: ES modules with named imports
- Async patterns: Async/await pattern preferred over promises
Environment
- Required vars:
INFLUXDB_TOKEN(authentication) - Optional vars:
INFLUXDB_URL(defaults to http://localhost:8086)INFLUXDB_ORG(organization name for queries)DEBUG=mcp:*(enables MCP protocol debugging)
Project Structure
src/- Core server implementationtests/- Integration tests using Docker containers
Testing Approach
- Integration tests use Docker to spin up a real InfluxDB instance
- Tests primarily use direct API communication for reliability
- Server process is tested through direct spawning and API verification
- All tests include proper cleanup of Docker containers
- Test timeout is set to 60 seconds to accommodate Docker operations
Common Issues
- Docker needs to be running for tests to pass
- Port conflicts can occur if other services are using port 8086
- MCP client connection issues are bypassed by using direct API testing
- Sometimes Docker cleanup requires manual intervention (docker rm)
- See TESTS.md for detailed troubleshooting guides
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 · 45 lines · 499 tokens per session scan A afbeee9c50e3
influxdb-mcp-server CLAUDE.md is an instructions file published in the GitHub repository idoru/influxdb-mcp-server (44 stars, last pushed 7mo ago), licensed MIT. It adds 499 tokens to every session, about $0.0025 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
lms-front CLAUDE.md
Claude Code instructions for guillermoscript/lms-front, covering claude.md, project overview, commands, architecture and multi-tenancy.
vespertide AGENTS.md
AGENTS.md instructions for dev-five-git/vespertide, covering vespertide knowledge base, structure, where to look, data flow and conventions.
seekstone CLAUDE.md
Claude Code instructions for shaqmughal/seekstone, covering claude.md, what this repo is, commands, the harness itself (run after npm install) and architecture.
rails_ai_agents AGENTS.md
AGENTS.md instructions for ThibautBaissac/rails_ai_agents, covering project configuration, tech stack, architecture, key commands and tests.
pg-dash CLAUDE.md
Claude Code instructions for indiekitai/pg-dash, covering pg-dash claude.md, 项目结构, 构建与测试, 发版纪律（强制） and 发版检查清单（每次 npm publish 前必须按序执行）.
MCP-SqlServer CLAUDE.md
Claude Code instructions for Aron-Valenzuela/MCP-SqlServer, covering claude.md, project overview, setup (for each user), 1. install dependencies and 2. configure claude desktop.