What is mcp-server-ipinfo AGENTS.md?

Repository instructions for developing and releasing the mcp-server-ipinfo project, a server that provides IP-information tools through MCP. They describe coding conventions, release files, automated publishing, and smoke tests.

Use them when changing this project, preparing a release, updating its version or changelog, regenerating the package manifest, running tests, or publishing a Python package and desktop bundle.

They give coding agents the project-specific rules needed to avoid inconsistent commits, stale generated files, and release failures. They explain which files are generated and which checks run before publishing.

How briandconnelly/mcp-server-ipinfo configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to briandconnelly/mcp-server-ipinfo. 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/briandconnelly/mcp-server-ipinfo/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/briandconnelly/mcp-server-ipinfo

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/briandconnelly/mcp-server-ipinfo/agents-md/github.svg)](https://agentmods.dev/instructions/briandconnelly/mcp-server-ipinfo/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/briandconnelly/mcp-server-ipinfo/agents-md"><img src="https://agentmods.dev/badge/instructions/briandconnelly/mcp-server-ipinfo/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/briandconnelly/mcp-server-ipinfo/agents-md"><img src="https://agentmods.dev/badge/instructions/briandconnelly/mcp-server-ipinfo/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 725 This file is loaded in full into every session.

When invoked 725 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.

Model	Per session	Once invoked
Fable 5.1	$0.00725	$0.00725
Opus 5	$0.00362	$0.00362
Sonnet 5	$0.00145	$0.00145
Haiku 4.5	$0.00072	$0.00072

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

Security

Grade A, and why

mcp-server-ipinfo 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 10d 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 · 37 lines

How it starts

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

AGENTS.md

Conventions

Use Conventional Commits for commit messages.
Follow the Keep a Changelog format for CHANGELOG.md.

Releases

Releases are automated by .github/workflows/publish.yml, which triggers on pushing a tag matching v*. The workflow runs the test suite, asserts the tag matches the pyproject.toml version, checks manifest.json is in sync, builds the package, publishes to PyPI via trusted publishing (OIDC — no API token needed), and creates the GitHub release with auto-generated notes and the built dist/* artifacts (wheel, sdist) attached. A dependent bundle job (reusable .github/workflows/mcpb.yml) then packs the MCPB bundle (dist/mcp-server-ipinfo-<version>.mcpb) for one-click Claude Desktop install and uploads it to the release.

manifest.json is generated from pyproject.toml plus the server's registered tools by scripts/gen_manifest.py — do not hand-edit it. tests/test_manifest.py and the workflow both run gen_manifest.py --check to catch a stale committed manifest.

To cut a release:

Bump version in pyproject.toml, regenerate the manifest with uv run python scripts/gen_manifest.py, and fold the CHANGELOG.md [Unreleased] section into a new [<version>] - <date> heading (and update the compare links at the bottom). The publish workflow asserts tag == pyproject and that the manifest is in sync, failing the release on a mismatch.
Run the smoke tests (see below) before tagging — the workflow runs the default suite but not the smoke suite.
Merge to main, then tag and push: git tag v<version> && git push origin v<version> (the v prefix matters — it's what the workflow triggers on).

Do not run uv build / uv publish by hand; pushing the tag does it. If you want curated release notes instead of the auto-generated ones, create or edit the GitHub release with the CHANGELOG section — the workflow attaches artifacts but does not overwrite an existing release body.

Read the full file on GitHub · 37 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.

10d ago First seen · 37 lines · 725 tokens per session scan A 762b18930dfd

Subscribe to this mod's changes

mcp-server-ipinfo AGENTS.md is an instructions file published in the GitHub repository briandconnelly/mcp-server-ipinfo (44 stars, last pushed 1mo ago), licensed MIT. It adds 725 tokens to every session, about $0.0036 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-30.

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

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,153 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

mcp-server-ipinfo: Instructions file for Codex