agentmods.dev

Search-mcp: Instructions file for Codex

AGENTS.md

Search-mcp AGENTS.md is an instructions file for Codex, OpenCode from ferre-z/Search-mcp. It costs 784 tokens per session, scanned A, original, MIT.

A set of project instructions for Eyes-MCP, covering how to build, test, lint, run its command-line tool, start its server, and understand its architecture.

In plain words
What is it for?
Guiding work on the Eyes-MCP TypeScript project, including verification commands, server setup, ports, and key system components.
Why use it?
It gives coding agents the project-specific facts they need to run and change the repository correctly.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is ferre-z/Search-mcp's own configuration. It tells Codex and OpenCode how to work on Search-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 Search-mcp configures →

not rated 0repo 2mo ago A scan 784 tokens original MIT
View source ↗ ferre-z/Search-mcp
Reuse

Borrowing it

Nothing to install: this file belongs to ferre-z/Search-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/ferre-z/Search-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/ferre-z/Search-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 Search-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/ferre-z/search-mcp/agents-md.svg)](https://agentmods.dev/instructions/ferre-z/search-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/ferre-z/search-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/ferre-z/search-mcp/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 784 This file is loaded in full into every session.
When invoked 784 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00784 $0.00784
Opus 5 $0.00392 $0.00392
Sonnet 5 $0.00157 $0.00157
Haiku 4.5 $0.00078 $0.00078

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

Security

Grade A, and why

Search-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 · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md — Eyes-MCP

Build & verify

  • npm run build — compile TypeScript to dist/.
  • npm run dev — run the server with tsx watch (uses .env via dotenv).
  • npm run test — run vitest once.
  • npm run lint — typecheck only (tsc --noEmit). There is no ESLint or Prettier config.

Running the CLI

  • npm run eyes — run the CLI directly via tsx; no build step needed.
  • bin/eyes.mjs — production CLI shim; requires npm run build first because it imports dist/cli/index.js.
  • The eyes command that end users install is dropped by scripts/install.sh / install.ps1; it is not the same as npm run eyes.

Running the server

  • npm run dev starts the MCP HTTP server locally.
  • docker compose up brings up the full stack: eyes-mcp, SearXNG, Redis, Crawl4AI.
  • Container listens on 8787 internally; the installer scripts map host port 51823 (override with EYES_PORT) to container port 8787.

Architecture facts

  • One LLM in the system (src/main-agent/). It decomposes the prompt, dispatches parallel source adapters, parses results, reviews, and synthesizes.
  • Adapters are no-LLM async fetchers. They write raw artifacts to {EYES_DATA_DIR}/shards/{shardId}.json; the parse layer reads those files; the main agent never sees raw bytes.
  • Streamable HTTP MCP with per-session McpServer + StreamableHTTPServerTransport pairs (multi-tenant). The server must connect the transport before handling requests (src/index.ts:116).
  • Dispatcher source categories: web, github, reddit, youtube, hackernews, arxiv, wikipedia. osm and generic adapters exist but currently map to web.

Configuration

  • CLI reads a TOML file at ~/.config/eyes/config.toml (XDG-aware via XDG_CONFIG_HOME), parsed by smol-toml.
  • The Docker server reads env vars only (.env or docker-compose.yml); it does not read the TOML.
  • Env always overrides file config. Legacy GEMINI_API_KEY still maps onto Google AI Studio.
  • Provider ids are google-ai-studio and openrouter.
  • Per-session rate limiting is intentionally not implemented in v0.1; it is deferred to v0.2.

Read the full file on GitHub · 49 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 · 49 lines · 784 tokens per session scan A bd75e690e02e

Subscribe to this mod's changes

Search-mcp AGENTS.md is an instructions file published in the GitHub repository ferre-z/Search-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 784 tokens to every session, about $0.0039 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.

Gemmaai-agentclaudecrawl4aidockergemini
Related

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.

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

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

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

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

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