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/nacho4d/mcp-web-search/agents-mdgit clone --depth 1 https://github.com/nacho4d/mcp-web-searchWrote 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/nacho4d/mcp-web-search/agents-md)<a href="https://agentmods.dev/instructions/nacho4d/mcp-web-search/agents-md"><img src="https://agentmods.dev/badge/instructions/nacho4d/mcp-web-search/agents-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 | $0.00472 | $0.00472 |
| Opus 5 | $0.00236 | $0.00236 |
| Sonnet 5 | $0.00094 | $0.00094 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
mcp-web-search 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 4d 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
AGENTS.md
Environment
- Package manager:
uv— useuv runanduv sync, notpip - Python version: 3.12+ (pinned in
pyproject.tomlviarequires-python) - No required environment variables — the server makes unauthenticated requests only
Commands
| Action | Command |
|---|---|
| Install dependencies | uv sync |
| Start server (stdio) | uv run mcp-web-search |
| Start server (HTTP) | uv run mcp-web-search --transport streamable-http --host 127.0.0.1 --port 8000 |
| Build wheel | uv build |
There is no test suite and no lint step at this time.
Tool contracts
Both tools always return a JSON string (never raise). The success field signals outcome.
search_list
- Returns up to 10 results from DuckDuckGo.
- Can fail with
DDGSException: Ratelimit— this is a transient DuckDuckGo rate-limit, not a code bug.
access_site
- Downloads up to 2 MB of raw bytes before cutting off.
- After HTML stripping, content is further capped at 20 000 characters. If truncated,
"truncated": trueis set and the string ends with[... content truncated ...]. - Non-HTML responses (JSON, plain text, etc.) are returned as-is up to the same character cap.
- The User-Agent is spoofed to a Chrome/Linux string — this is intentional to avoid bot-blocking.
Boundaries
Always
- Keep both tools returning JSON strings; never change them to raise exceptions.
- Verify the server starts cleanly (
uv run mcp-web-search) before finishing any task.
Ask First
- Adding any new dependency to
pyproject.toml - Adding a third tool — the two-tool surface is intentional
- Changing default transport, host, or port values
Never
- Commit secrets, API keys, or
.envfiles - Remove the 2 MB download cap or the 20 000-character text cap without explicit instruction — they exist to protect Claude's context window
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.
- 4d ago First seen · 48 lines · 472 tokens per session scan A 3ad1e6ac28ea
mcp-web-search AGENTS.md is an instructions file published in the GitHub repository nacho4d/mcp-web-search (0 stars, last pushed 2mo ago), licensed MIT. It adds 472 tokens to every session, about $0.0024 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).
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.
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).