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/setlist-mcp/claude-mdgit clone --depth 1 https://github.com/chrischall/setlist-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/setlist-mcp/claude-md)<a href="https://agentmods.dev/instructions/chrischall/setlist-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/chrischall/setlist-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.03431 | $0.03431 |
| Opus 5 | $0.01716 | $0.01716 |
| Sonnet 5 | $0.00686 | $0.00686 |
| Haiku 4.5 | $0.00343 | $0.00343 |
Grade A, and why
setlist-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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
setlist-mcp
MCP server for setlist.fm. Wraps the setlist.fm REST API (https://api.setlist.fm/rest) and exposes 20 tools to Claude over stdio: 18 read-only (the REST API has no write endpoints — those are all GETs) plus 2 authenticated "I was there" attendance actions (setlist_mark_attended / setlist_unmark_attended) performed against the logged-in website (Apache Wicket), not the REST API.
Commands
npm run build # tsc + esbuild bundle → dist/index.js + dist/bundle.js
npm test # tsc typecheck + vitest run
npm run test:watch # vitest watch
npm run test:coverage # tsc typecheck + vitest run --coverage (v8 reporter, no thresholds)
Run locally (requires built dist/):
SETLIST_API_KEY=xxx node dist/index.js
Tool naming
All tools are prefixed setlist_ (e.g. setlist_search_setlists, setlist_get_artist).
Architecture
src/
version.ts # single source of truth for VERSION (x-release-please-version)
index.ts # MCP server entry — runMcp({ name, version, banner, tools })
client.ts # SetlistClient — reads SETLIST_API_KEY, attaches x-api-key
# header per request, 15s request timeout + 2s 429 retry (both
# via createApiClient), normalizes response eventDate → ISO
# (deepMapStringField + dmyToIso from @chrischall/mcp-utils),
# then augmentSetlists(...) annotates each setlist
augment.ts # augmentSetlists — walks a response, tags every setlist object
# with songCount / setCount / hasSongs so callers skip empty stubs
web-client.ts # SetlistWebClient — authenticated www.setlist.fm (website) client
# for the attendance writes; session-cookie auth, 5xx retry,
# serialized write pacer (see attendance gotcha)
fetchproxy-cookie.ts # resolveSessionCookie — shared createAuthResolver
# (mcp-utils) three-path resolver: SETLIST_SESSION_COOKIE →
# one-shot fetchproxy browser-bridge grab (15s withDeadline)
# → actionable error (lazy; @fetchproxy/bootstrap)
attribution.ts # ATTRIBUTION_NOTE appended to data tool descriptions
view.ts # SETLIST_VIEWS / viewArg / viewResponse — the fleet `view`
# vocabulary. compact = stripMediaUrls only (no field
# projection; see the docblock), full = untouched. Every
# read tool answers through viewResponse; writes do not
tools/
artists.ts # setlist_search_artists, setlist_get_artist, setlist_get_artist_setlists
setlists.ts # setlist_search_setlists, setlist_get_setlist, setlist_get_setlist_version
venues.ts # setlist_search_venues, setlist_get_venue, setlist_get_venue_setlists
geo.ts # setlist_search_cities, setlist_get_city, setlist_search_countries
users.ts # setlist_get_user, setlist_get_user_attended, setlist_get_user_edited
resolve.ts # setlist_resolve_concerts (batch {artist,date,city?,venue?} → setlist resolver)
attendance.ts # setlist_mark_attended, setlist_unmark_attended (authenticated website writes via web-client.ts)
urls.ts # setlist_id_from_url (pure local parser — extracts the setlist ID from a /setlist/ URL)
utilities.ts # setlist_healthcheck
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 · +4 lines · +229 tokens per session 2f2c9c186636
- 5d ago First seen · 128 lines · 3,202 tokens per session scan A 7ecdea042b41
setlist-mcp CLAUDE.md is an instructions file published in the GitHub repository chrischall/setlist-mcp (0 stars, last pushed today), licensed MIT. It adds 3,431 tokens to every session, about $0.0172 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).
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.
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).
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.