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/null-create/shodan-mcp-server/agents-mdgit clone --depth 1 https://github.com/null-create/shodan-mcp-serverWhat 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.01189 | $0.01189 |
| Opus 5 | $0.00594 | $0.00594 |
| Sonnet 5 | $0.00238 | $0.00238 |
| Haiku 4.5 | $0.00119 | $0.00119 |
Grade A, and why
shodan-mcp-server 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 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions for mcp-shodan-server
Project Overview
An MCP (Model Context Protocol) server that exposes the Shodan API as MCP tools. Built with FastMCP and the official shodan library.
Key Files
| File | Purpose |
|---|---|
server.py |
Entry point — creates FastMCP app, initializes Shodan client via init_client(), wraps tool functions with @mcp.tool(), serves via HTTPS (uvicorn + Starlette) |
tools/shodan.py |
All 30 tool implementations as standalone functions + module-level _client singleton + init_client() factory |
requirements.txt |
Python dependencies (fastmcp, mcp, shodan, uvicorn, starlette) |
.env |
Environment config (SHODAN_API_KEY, HOST_PORT, HOST_ADDRESS, SSL_CERTFILE, SSL_KEYFILE, CORS_ORIGINS) |
Dockerfile / docker-compose.yml |
Container setup |
Architecture (Two-Layer Design)
server.py tools/shodan.py
┌────────────────────┐ ┌──────────────────────┐
│ @mcp.tool() │ │ def shodan_search() │
│ def shodan_search()│─────▶│ client = _client │
│ return shodan_ │ │ try/except │
│ tools.search() │ │ return client... │
│ │ │ │
│ @mcp.tool() │ │ def shodan_host() │
│ def shodan_host() │─────▶│ ... │
│ ... │ └──────────────────────┘
└────────────────────┘
MCP decorators ▶ Pure API logic
(tool descriptions) (no MCP dependency)
server.py: MCP layer — importstools.shodanmodule +init_client(), defines@mcp.tool()wrappers that delegate to the tool functionstools/shodan.py: API layer — standalone functions, module-level_clientsingleton, try/except error handlingtools/shodan.pyhas no MCP dependency (nofrom mcp.server import FastMCP)- All tools catch
shodan.APIErrorand return{"error": str(e)}instead of raising init_client(api_key)is called once at startup inserver.pyto set the module-level_client
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 · 113 lines · 1,189 tokens per session scan A dffe09fbde05
shodan-mcp-server AGENTS.md is an instructions file published in the GitHub repository null-create/shodan-mcp-server (0 stars, last pushed 2mo ago), licensed MIT. It adds 1,189 tokens to every session, about $0.0059 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
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.
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).
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.