surfmeter-mcp: Instructions file for Codex

AGENTS.md

surfmeter-mcp AGENTS.md is an instructions file for Codex, OpenCode from aveq-research/surfmeter-mcp. It costs 1,105 tokens per session, scanned A, original, MIT.

A repository instruction file describing how to work on the Surfmeter MCP project, including its commands, architecture, tests, and API operation catalogue.

In plain words
What is it for?
It helps agents install dependencies, type-check, test, build, format, run optional integrations, and add operations to the API wrapper.
Why use it?
It gives a coding agent the project-specific rules and checks needed to make changes safely and consistently.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is aveq-research/surfmeter-mcp's own configuration. It tells Codex and OpenCode how to work on surfmeter-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything surfmeter-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to aveq-research/surfmeter-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/aveq-research/surfmeter-mcp/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/aveq-research/surfmeter-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.

agentmods badge for surfmeter-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/aveq-research/surfmeter-mcp/agents-md.svg)](https://agentmods.dev/instructions/aveq-research/surfmeter-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/aveq-research/surfmeter-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/aveq-research/surfmeter-mcp/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,105 This file is loaded in full into every session.
When invoked 1,105 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01105 $0.01105
Opus 5 $0.00553 $0.00553
Sonnet 5 $0.00221 $0.00221
Haiku 4.5 $0.00111 $0.00111

Measured 6d ago against content hash 978a79d07e49, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

surfmeter-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 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.

AGENTS.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 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.

Commands

Node.js 20+ and pnpm 10 are required.

  • pnpm install — install dependencies
  • pnpm check — type check without emitting
  • pnpm test — run all vitest suites; the integration suites skip themselves when credentials are absent
  • pnpm vitest run test/mcp.test.ts — run a single test file
  • pnpm vitest run -t "reports validation errors" — run a single test by name
  • pnpm build — compile to build/ and mark build/index.js executable
  • pnpm test:all — type check, test, and build together; run this before committing
  • pnpm format / pnpm format:check — Biome formatting (only the formatter is enabled, there are no lint rules)

The integration tests need a reachable Surfmeter development server and send read-only requests only:

API_ENDPOINT=http://localhost:3001 \
API_KEY=client_admin-replace-me \
pnpm test:integration

Add SURFMETER_FULL_INTEGRATION=1 to also run the extended pass that reads every collection, both search services, settings, and AI status.

Architecture

The server is a thin, layered wrapper around one HTTP API. Requests flow index.ts (stdio bootstrap) → server.ts (McpServer plus the host-facing instructions string) → tools.ts (schemas, safety categories, handlers) → client.ts (HTTP, X-API-KEY, error mapping) → result.ts (wrapping into CallToolResult).

config.ts turns API_ENDPOINT into a complete management endpoint: it appends /client_admin_api/v1 unless the value already ends with it, so both a server origin and a full endpoint work. Handlers therefore pass bare paths such as clients/7.

client.ts handles both plain JSON and Elasticsearch NDJSON scroll responses, and raises SurfmeterApiError carrying the status and the parsed error body. result.ts converts thrown errors into isError tool results instead of protocol errors, so tool failures stay readable to the model.

Read the full file on GitHub · 64 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.

  1. 6d ago First seen · 64 lines · 1,105 tokens per session scan A 978a79d07e49

Subscribe to this mod's changes

surfmeter-mcp AGENTS.md is an instructions file published in the GitHub repository aveq-research/surfmeter-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,105 tokens to every session, about $0.0055 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.

Related

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

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.

github/spec-kit · 7,104 tokens