registry: Instructions file for Codex

AGENTS.md

registry AGENTS.md is an instructions file for Codex, OpenCode from mercantry/registry. It costs 1,112 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for AI agents working with or using Mercantry, an open registry of restaurant information and booking services in Los Angeles, Hong Kong, and Tokyo.

In plain words
What is it for?
Connecting to Mercantry, using its remote or local tools, accessing its REST API, and working on the codebase according to its documented layout and rules.
Why use it?
They explain which tools, commands, files, and project rules an agent should use, reducing mistakes when navigating the repository or registry.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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 registry AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/mercantry/registry/agents-md/github.svg)](https://agentmods.dev/instructions/mercantry/registry/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/mercantry/registry/agents-md"><img src="https://agentmods.dev/badge/instructions/mercantry/registry/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.

agentmods 80×15 button for registry AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/mercantry/registry/agents-md"><img src="https://agentmods.dev/badge/instructions/mercantry/registry/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,112 This file is loaded in full into every session.
When invoked 1,112 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.01112 $0.01112
Opus 5.5 $0.00445 $0.00445
Sonnet 5.5 $0.00222 $0.00222
Haiku 4.5 $0.00111 $0.00111

Measured 2mo ago against content hash 96b0cb9e236a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

registry 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 2mo 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 · 59 lines

How it starts

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

AGENTS.md — guide for AI agents in this repository

This file follows the AGENTS.md convention. Two kinds of agents end up here: agents using the registry (you want the MCP tools) and agents working on the codebase (you want the commands and invariants).

If you want to USE the registry

Mercantry is an open commerce registry for AI agents — structured merchant data, honest signals, and real-world booking fulfillment across Los Angeles, Hong Kong, and Tokyo. Read docs/mcp-tools.md — it is written for LLM tool selection, with example transcripts. Summary:

  • Connect remotely over Streamable HTTP — claude mcp add --transport http mercantry https://mercantry.org/mcp — or locally over stdio (npm run mcp). Both transports serve the identical tool surface. A REST mirror lives at /v1 (OpenAPI at /v1/openapi.json; self-serve keys: POST /v1/keys with developer_name + contact; bulk export: GET /v1/export/merchants.ndjson — bulk ingestion, caching, and training on the data are permitted per the open license).
  • Fulfillment is human-operated (voice automation is deferred): real bookings are accepted only for phone-verified bookable merchants and are worked during 12:00–23:00 Asia/Shanghai (04:00–15:00 UTC), with an honest queue + 24h auto-fail. sandbox: true merchants give deterministic test outcomes and never touch a real restaurant. Check get_registry_meta for current coverage and verification counts before assuming anything.
  • Read tools: search_merchants (filter-based, never ranked, deterministic order), get_merchant (full signal dump), get_availability (honest: checks happen at booking time), get_registry_meta (evaluate the registry itself, staleness included).
  • Booking is async: place_booking → poll get_booking_status or pass callback_url. Set accept_within_window: true so merchant counter-offers inside your window confirm without a round-trip.
  • Always cancel_booking when plans change. No-shows are tracked per developer key; high no-show keys get throttled.
  • submit_feedback only after a confirmed booking, once, within 14 days.

Read the full file on GitHub · 59 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. 2mo ago First seen · 59 lines · 1,112 tokens per session scan A 96b0cb9e236a

Subscribe to this mod's changes

registry AGENTS.md is an instructions file published in the GitHub repository mercantry/registry (0 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 1,112 tokens to every session, about $0.0044 per session on Opus 5.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.

Related

registry AGENTS.md compared with instructions from other repositories

registry AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
registry AGENTS.mdmercantry/registryInstructions file03mo agoApache-2.0A1,112Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file275k3d agoMITA4,313Codex, OpenCode