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/sixflags-mcp/claude-mdgit clone --depth 1 https://github.com/chrischall/sixflags-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/sixflags-mcp/claude-md)<a href="https://agentmods.dev/instructions/chrischall/sixflags-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/chrischall/sixflags-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.02634 | $0.02634 |
| Opus 5 | $0.01317 | $0.01317 |
| Sonnet 5 | $0.00527 | $0.00527 |
| Haiku 4.5 | $0.00263 | $0.00263 |
Grade A, and why
sixflags-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 today.
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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sixflags-mcp
MCP server for Six Flags theme parks — live wait times, park hours, show schedules, attraction directory, and day-planning. Backed by the public, keyless themeparks.wiki v1 API. One entry point: stdio (src/index.ts, the npm/mcpb package). Built on @chrischall/mcp-utils (the fleet's rate-limited-public-API / no-auth-reads archetype — see mcp-utils/skills/mcp-fleet-builder/SKILL.md).
Commands
npm run build # tsc → dist/, then esbuild bundle → dist/bundle.js
npm test # vitest run
npm run test:coverage # vitest with the 100% coverage gate (CI)
npm run test:watch # vitest in watch mode
npm run dev # node --env-file=.env dist/index.js (requires a build)
dist/ is gitignored — produced at build/release time and shipped in the npm package (package.json files).
Architecture
src/
index.ts stdio entry — runMcp() from @chrischall/mcp-utils; builds a ParkDirectory (the dep) and applies the tool registrars. No auth step (keyless upstream).
version.ts VERSION — the single release-please version marker. Imported by the entry point.
protocol.ts Wire constants: BASE_URL (api.themeparks.wiki), getDefaultHeaders (Accept + User-Agent), getRequestTimeoutMs. Leaf module.
client.ts SixFlagsClient — a thin wrapper over createApiClient with NO token resolver (public API → no Authorization header). Exposes request<T>(method, path). Loads .env for local dev.
config.ts getHomePark() → SIXFLAGS_HOME_PARK or "Carowinds".
parks.ts ParkDirectory — fetches /v1/destinations, filters to the Six Flags chain by slug, flattens to individual parks, memoizes (12h TTL), and resolves a name/slug/substring/id (or the home park) to a park entity id. Carries the client on `.client`.
tools/
_shared.ts jsonResponse + the /live zod schema (fetchLive), attraction normalization (normalizeAttractions), anyRideOperating, byWaitDescending.
parks.ts sixflags_list_parks, sixflags_get_park_schedule
waittimes.ts sixflags_get_wait_times, sixflags_suggest_next
attractions.ts sixflags_list_attractions, sixflags_get_shows
health.ts sixflags_healthcheck
tests/ mirrors src/; mocks SixFlagsClient.request via vi.spyOn (see tests/_fixtures.ts). server-boot.test.ts drives the real built artifacts.
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.
- today Changed · +6 lines · +300 tokens per session 11a77b007662
- 5d ago First seen · 94 lines · 2,334 tokens per session scan A 359f73721ee1
sixflags-mcp CLAUDE.md is an instructions file published in the GitHub repository chrischall/sixflags-mcp (0 stars, last pushed today), licensed MIT. It adds 2,634 tokens to every session, about $0.0132 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
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 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.
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.
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).