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/him229/stays/claude-mdgit clone --depth 1 https://github.com/him229/staysWrote 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/him229/stays/claude-md)<a href="https://agentmods.dev/instructions/him229/stays/claude-md"><img src="https://agentmods.dev/badge/instructions/him229/stays/claude-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.04053 | $0.04053 |
| Opus 5 | $0.02027 | $0.02027 |
| Sonnet 5 | $0.00811 | $0.00811 |
| Haiku 4.5 | $0.00405 | $0.00405 |
Grade A, and why
stays CLAUDE.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.
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
stays is a Python library and MCP server that provides programmatic access to Google Hotels through direct API interaction (reverse engineering). The project consists of:
- MCP server (
stays/mcp/) — FastMCP-based stdio + streamable-HTTP server exposing three tools. Layered intoserver.py(registration only —@mcp.tool/@mcp.prompt/@mcp.resource+ re-exports),_config.py(HotelSearchConfig,CONFIG,CONFIG_SCHEMA,HARD_MAX_HOTELS_WITH_DETAILS = 15),_params.py(pydantic*Paramsclasses + shared_validate_child_ages), and_executors.py(_execute_*_from_params+ MCP-subset_serialize_hotel_*wrappers). - Search engine (
stays/search/) — hotel search, detail, and parallel enrichment - Core client (
stays/search/client.py) — rate-limitedcurl_cffisession with Chrome TLS impersonation - Data models (
stays/models/google_hotels/) — pydantic filter/result/detail models - Parse layer (
stays/search/parse/) — response parsing split acrosssearch_parser/detail_parser/policy_parser/provider_parser/slots.py.slots.pyowns named slot-index constants +safe_get(tree, *path, default). - Canonical serializers (
stays/serialize.py) — single source of truth for hotel → dict serialization consumed by both the CLI and MCP (the CLI-localstays/cli/_serialize.pyis a re-export shim). - CLI runtime helpers (
stays/cli/_runtime.py) — sharedemit_result/emit_error/build_filters_from_cli_argsplumbing used bysearch/details/enrichsubcommands. - MCP setup backends (
stays/mcp/setup/_backend.py+_adapters.py) —SetupBackendProtocol +SetupReportdataclass +BACKENDSregistry; the legacystays.mcp.setup.{claude,codex,chatgpt}.register(...)/.build()entry points are preserved on top.
The implementation leans heavily on reverse-engineering captures under docs/reverse-engineering/ — slot maps and filter coverage notes are the authoritative reference for the wire format.
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 · 205 lines · 4,053 tokens per session scan A cec69602ea2f
stays CLAUDE.md is an instructions file published in the GitHub repository him229/stays (12 stars, last pushed 10d ago), licensed MIT. It adds 4,053 tokens to every session, about $0.0203 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.
Other instructions, from other repositories
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.
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.