Borrowing it
Nothing to install: this file belongs to semidark/mcp-litellm-searxng. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/semidark/mcp-litellm-searxng/main/AGENTS.mdgit clone --depth 1 https://github.com/semidark/mcp-litellm-searxngWrote 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/semidark/mcp-litellm-searxng/agents-md)<a href="https://agentmods.dev/instructions/semidark/mcp-litellm-searxng/agents-md"><img src="https://agentmods.dev/badge/instructions/semidark/mcp-litellm-searxng/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/semidark/mcp-litellm-searxng/agents-md"><img src="https://agentmods.dev/badge/instructions/semidark/mcp-litellm-searxng/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00389 | $0.00389 |
| Opus 5 | $0.00195 | $0.00195 |
| Sonnet 5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
mcp-litellm-searxng 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 9d 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
Overview
- Single-package npm repo. No build, lint, typecheck, or CI config is present.
- Runtime entrypoint is root
index.js; published package only includesindex.js,README.md, andLICENSE. - Node requirement is
>=18; package is ESM ("type": "module").
Code Shape
- The whole MCP server lives in
index.js. - It registers exactly one tool,
web_search, over stdio using@modelcontextprotocol/sdk. VERSIONis hardcoded inindex.jsand also stored inpackage.json; keep both in sync when bumping releases.
Verification
npm startruns the server directly:node index.js.npm testruns the only repo-local test harness:node test.js.test.jsis an integration test against a real LiteLLM endpoint, not a unit test. It requiresLITELLM_SEARCH_URLandLITELLM_API_KEYin the environment and will fail fast without them.
Gotchas
- Server startup exits immediately if
LITELLM_SEARCH_URLorLITELLM_API_KEYis missing. LITELLM_TIMEOUT_MSdefaults to30000; timeout behavior is implemented inindex.jswithAbortController.test.jsresolves the repo root fromimport.meta.url; keep it portable if you refactor file layout.structuredContent.resultsintentionally returns the raw result array whilecontentcarries the formatted text block.npx -y @semidark/mcp-litellm-searxngworks from outside the repo, but npm 11 on Node 25 can mis-resolve it when run from inside this package checkout. Use an isolated--prefixwhen testing the published package locally.
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.
- 9d ago First seen · 26 lines · 389 tokens per session scan A f33675afa00b
mcp-litellm-searxng AGENTS.md is an instructions file published in the GitHub repository semidark/mcp-litellm-searxng (0 stars, last pushed 3mo ago), licensed MIT. It adds 389 tokens to every session, about $0.0019 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
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 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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.