google-hotels-mcp: Instructions file for Codex

AGENTS.md

google-hotels-mcp AGENTS.md is an instructions file for Codex, OpenCode from alexechoi/google-hotels-mcp. It costs 719 tokens per session, scanned A, original, MIT.

Project instructions for google-hotels-mcp, including how Concord coordinates shared work between coding agents.

In plain words
What is it for?
Use it when editing this project, especially to start work, inspect assignments, update or transfer tasks, and finish with evidence about changes and tests.
Why use it?
It helps agents claim work, detect overlapping changes, share progress, and record a clear completion handoff.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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 google-hotels-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/alexechoi/google-hotels-mcp/agents-md.svg)](https://agentmods.dev/instructions/alexechoi/google-hotels-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/alexechoi/google-hotels-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/alexechoi/google-hotels-mcp/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 719 This file is loaded in full into every session.
When invoked 719 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.00719 $0.00719
Opus 5 $0.00360 $0.00360
Sonnet 5 $0.00144 $0.00144
Haiku 4.5 $0.00072 $0.00072

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

Security

Grade A, and why

google-hotels-mcp 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 6d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 56 lines

How it starts

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

Concord — shared work-state for coding agents

This project uses Concord MCP. Keep coordination to the five workflow tools:

  • Before editing, call start_work with the task, your agent kind, and expected files or modules. It registers presence, accepts assigned work when appropriate, claims the scope, and returns overlap warnings. Concord derives your agent_id from your session — omit it unless your client told you one.
  • Use inspect_work to read the workspace, one task, one agent, or one message thread. Use update_work for durable progress and for live prompts/replies to another promptable workspace agent, including while that agent is busy.
  • Use transfer_work for assignment, acceptance, decline, release, reassignment, evidence-bearing handoff offers, and reopening.
  • Before finishing, call finish_work once with the outcome, changed files, tests, assumptions, decisions, risks, guardrails, and provenance. It records evidence and can mark work review-ready or terminal.

Keep each claim small and resolve reported overlaps before editing. Concord regenerates human-readable review artifacts in .concord/.

Enforcement remains client-dependent. concord doctor reports setup and workflow adoption; optional hooks can block exact-file collisions.

Project: ghotels (Google Hotels MCP)

Ground-up rewrite of the unmaintained him229/stays. One typed core serves three surfaces: MCP server, CLI, Python library. PyPI name: ghotels.

Commands

  • make check — everything CI runs (ruff format --check, ruff check, mypy --strict, offline pytest)
  • make test / make test-live — offline suite / live end-to-end tier (network)
  • uv run ghotels --help — the CLI; ghotels mcp runs the stdio MCP server

Architecture (src/ghotels/)

  • models/ — pure pydantic domain models; semantic string enums, NO wire IDs
  • protocol/ — request side: wire IDs (ids.py), payload builders (request.py), envelope decode (response.py). Slot map documented in docs/PROTOCOL.md
  • parsing/ — response side: entry walker, detail parser, cancellation deadlines anchored to check-in date (never date.today() — that bug class broke upstream CI)
  • transport.py — async curl_cffi (Chrome TLS), token bucket (GHOTELS_RPS), tenacity retries
  • api.pyAsyncGoogleHotels + sync GoogleHotels facade (private loop thread)
  • envelope.py — canonical JSON envelopes shared by CLI and MCP
  • cli/, mcp/ — thin surfaces over the core

Read the full file on GitHub · 56 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. 6d ago First seen · 56 lines · 719 tokens per session scan A b3fbf6efbb80

Subscribe to this mod's changes

google-hotels-mcp AGENTS.md is an instructions file published in the GitHub repository alexechoi/google-hotels-mcp (2 stars, last pushed 26d ago), licensed MIT. It adds 719 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-31.

Related

Other instructions, from other repositories

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

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

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens