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/repliers-io/mcp-server/claude-mdgit clone --depth 1 https://github.com/Repliers-io/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/repliers-io/mcp-server/claude-md)<a href="https://agentmods.dev/instructions/repliers-io/mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/repliers-io/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.01225 | $0.01225 |
| Opus 5 | $0.00613 | $0.00613 |
| Sonnet 5 | $0.00245 | $0.00245 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade A, and why
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 yesterday.
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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repliers MCP Server — Agent Instructions
MCP server exposing the Repliers MLS API to AI agents (claude.ai connectors, IDE agents, custom clients). Node.js 22+, ESM, @modelcontextprotocol/sdk. Two transports in one entry point: stdio (default) and Streamable HTTP.
Commands
node mcpServer.js # stdio transport
node mcpServer.js --http # Streamable HTTP on PORT (default 3001), endpoint /mcp
npm test # node --test test/**/*.test.js
npm run list-tools # print the tool roster (index.js CLI)
npm run generate # regenerate tools/…/generated/ from openapi.json
Architecture
| Path | Role |
|---|---|
mcpServer.js |
Server entry: both transports, session handling, attaches _feedback nudges to every tool response via lib/feedbackHints.js, serves instructions from lib/serverInstructions.js |
lib/tools.js |
discoverTools() — loads every .js from tools/repliers/repliers-api/{generated,custom}/ exporting apiTool |
tools/repliers/repliers-api/generated/ |
39 tools generated from openapi.json (npm run generate) — CRM, estimates, locations, saved searches… Do not edit by hand |
tools/repliers/repliers-api/custom/ |
6 hand-written tools: search-listings (NLP search + appliedFilters enrichment), refine-search, send-feedback, statistics, get-parameter-enumerations, get-listing-image |
lib/apiBase.js |
apiBaseUrl() / apiOrigin() — the only place the API host is written. Generated tools import it (the codegen template emits the call, so regeneration preserves it); never hardcode the host anywhere else |
lib/appliedFilters.js |
Parses the NLP-built listing URL into the human-readable appliedFilters summary, and flags params the API discards in appliedFilters.unrecognized (checked against the /listings parameter set in openapi.json, read lazily — /nlp reports unrecognizedParams: [] even when /listings rejects the param) |
lib/feedbackHints.js |
Failure detectors (no-location-filter, zero-results, api-error…) + eagerness levels → _feedback block |
lib/feedbackCard.js, lib/trello.js |
Feedback card formatting + Trello REST delivery |
test/ |
Unit tests (node:test), one file per lib/tool module |
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.
- yesterday First seen · 56 lines · 1,225 tokens per session scan A d7c62f01a8ec
mcp-server CLAUDE.md is an instructions file published in the GitHub repository Repliers-io/mcp-server (17 stars, last pushed today), licensed MIT. It adds 1,225 tokens to every session, about $0.0061 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-09-04.
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).
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.
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).