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/chrischall/getyourguide-mcp/claude-mdgit clone --depth 1 https://github.com/chrischall/getyourguide-mcpWrote 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/chrischall/getyourguide-mcp/claude-md)<a href="https://agentmods.dev/instructions/chrischall/getyourguide-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/chrischall/getyourguide-mcp/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.1 | $0.01285 | $0.01285 |
| Opus 5 | $0.00642 | $0.00642 |
| Sonnet 5 | $0.00257 | $0.00257 |
| Haiku 4.5 | $0.00128 | $0.00128 |
Grade A, and why
getyourguide-mcp 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 5d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
getyourguide-mcp
MCP server for GetYourGuide tours & activities, built on the
GetYourGuide Partner API
(https://api.getyourguide.com/1, auth header X-ACCESS-TOKEN). A
bearer/direct-API archetype fleet repo on @chrischall/mcp-utils — see
~/git/mcp-utils/skills/mcp-fleet-builder/SKILL.md for the shared
conventions; this file covers only what's specific here.
Commands
npm install
npm run build # tsc + esbuild bundle → dist/ (bin: dist/index.js, mcpb: dist/bundle.js)
npm test # tsc typecheck + vitest run
npm run test:coverage # the CI gate: tsc typecheck, then 100% lines/branches/functions/statements on src/ (index.ts excluded)
npx vitest run tests/client.test.ts # single file
Architecture
src/
index.ts # bootstrap — runMcp({ name, version, deps: client, tools })
version.ts # single VERSION source (x-release-please-version marker)
client.ts # GYGClient — GET wrapper over createApiClient({ tokenHeader: 'X-ACCESS-TOKEN' })
# (its non-Bearer token mode); deferred GYG_API_KEY config error; one 429/503
# retry honoring a capped Retry-After; failures re-mapped to McpToolError + hint
validate.ts # parseGYG — thin wrapper over mcp-utils parseLenient: warn to stderr + return RAW on mismatch
tools/_shared.ts # jsonResponse, currency/language/pagination atoms, compact tour projection
tools/tours.ts # gyg_search_tours / gyg_get_tour / gyg_get_tour_options / gyg_get_tour_availability / gyg_get_tour_reviews
tools/taxonomy.ts # gyg_list_categories / gyg_list_category_tours / gyg_get_location / gyg_list_location_tours
tests/ # vitest; NO network — client tests inject fetchFn/sleepFn, tool tests spy client.get
All 9 tools are read-only GETs — no write tools, so no confirm gates.
Env: GYG_API_KEY (required at call time, deferred at boot), GYG_CURRENCY /
GYG_LANGUAGE (defaults, per-call args override), GYG_BASE_URL,
GYG_REQUEST_TIMEOUT_MS.
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.
- 5d ago First seen · 84 lines · 1,285 tokens per session scan A e49fe3bd123b
getyourguide-mcp CLAUDE.md is an instructions file published in the GitHub repository chrischall/getyourguide-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 1,285 tokens to every session, about $0.0064 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
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.
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).
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.
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.
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.