Borrowing it
Nothing to install: this file belongs to chrischall/accessoticketing-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.
curl -O https://raw.githubusercontent.com/chrischall/accessoticketing-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/chrischall/accessoticketing-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/accessoticketing-mcp/claude-md)<a href="https://agentmods.dev/instructions/chrischall/accessoticketing-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/chrischall/accessoticketing-mcp/claude-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.
<a href="https://agentmods.dev/instructions/chrischall/accessoticketing-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/chrischall/accessoticketing-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.00619 | $0.00619 |
| Opus 5 | $0.00309 | $0.00309 |
| Sonnet 5 | $0.00124 | $0.00124 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
accessoticketing-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 8d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
accessoticketing-mcp — repo notes
MCP server over accesso Passport mobile ticket links. Read docs/ACCESSO-API.md
before changing anything that touches the wire.
Shape
src/parse.ts— HTML →AccessoOrder. All the hard-won knowledge lives here.src/client.ts— fetch, redirect resolution, the accesso-host allowlist, error mapping.src/present.ts— projections for tool output (and the reason barcodes never reachtextResult).src/io.ts— the file-output boundary, so hosted deployments don't report paths nobody can open.src/tools/tickets.ts— the six read-only tools.
Things that will bite you
- The ticket URL is a credential.
oTokengrants the order. Never log it, never put one in a fixture, never commit one.redactUrlexists for this; use it on any path that renders a URL. - An expired link returns HTTP 200 with "no tickets available to print on this
order". Status codes tell you nothing here — gate on the body (
isExpiredOrderPage). - Every ticket is rendered twice. A mobile
#ticket-item-container<N>grouping and a.desktopTicketGroupingone, sharingimg#barcode<N>ids. Only the mobile blocks carry the container id, which is why the selector is what it is. - The detail panel is a sibling, not a child.
#flip-ticket-info-container<N>hangs off#ticket-grouping-containeralongside the ticket block. Guest Number, Web Sales ID, Instructions and Terms all live there and must be joined back by index. ticketIdis in neither rendering — only in the trailing "Register this ticket" modal forms, in ticket order. The mapping is positional and is refused (with a warning) when the counts disagree. Do not "fix" that by guessing: a shifted map hands out wallet links for the wrong tickets.- The host allowlist in
client.tsis a security boundary. These tools take a URL from the model; without it the server is an SSRF proxy. Don't widen it casually.
Fixtures
tests/fixtures/order.html is a real 12-ticket order with tokens, names, order number,
guest numbers and ticketIds all replaced, and the barcodes swapped for a 1×1 PNG. If you
re-capture, sanitize the same way and re-run the leak scan before committing.
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.
- 8d ago First seen · 45 lines · 619 tokens per session scan A 4bb74cd80abc
accessoticketing-mcp CLAUDE.md is an instructions file published in the GitHub repository chrischall/accessoticketing-mcp (0 stars, last pushed today), licensed MIT. It adds 619 tokens to every session, about $0.0031 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
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.
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).
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).
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.
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.