Borrowing it
Nothing to install: this file belongs to adamayoung/TMDb. 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/adamayoung/TMDb/main/CLAUDE.mdgit clone --depth 1 https://github.com/adamayoung/TMDbWrote 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/adamayoung/tmdb/claude-md)<a href="https://agentmods.dev/instructions/adamayoung/tmdb/claude-md"><img src="https://agentmods.dev/badge/instructions/adamayoung/tmdb/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.02244 | $0.02244 |
| Opus 5 | $0.01122 | $0.01122 |
| Sonnet 5 | $0.00449 | $0.00449 |
| Haiku 4.5 | $0.00224 | $0.00224 |
Grade A, and why
TMDb 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 — 174 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 when working with code in this
repository. It carries the always-on rules; the detail behind them lives in
topic docs under .claude/docs/ — read the relevant doc
before working in its area (see the table below).
Project Overview
TMDb is a Swift Package for The Movie Database API, supporting iOS 16+, macOS 13+, watchOS 9+, tvOS 16+, visionOS 1+, and Linux. Built with Swift 6.1+ and strict concurrency. (Windows is deliberately not claimed — no CI job builds it; see PR #374, which dropped the claim.)
TMDbClient is the main facade over protocol-based services with dependency
injection; the Apple-only on-device intelligence features ship as the separate
TMDbIntelligence product (with test doubles in TMDbIntelligenceTesting),
so the core TMDb product carries no API that cannot function on Linux.
Topic Docs
| Doc | Read before… |
|---|---|
architecture.md |
changing services, networking, models or the intelligence products; adding a feature |
testing.md |
writing or organising tests; adding a test target (names are hardcoded in five places) |
tmdb-api.md |
any work shaped by the live API — new endpoints, model changes, fixtures, probe scripts |
workflow.md |
running a delivery, filing issues, code review, the completion checklist, opening a PR |
tooling.md |
building/testing; choosing make vs skills vs Xcode; worktree/scratch-path isolation; the .xctestplan files (gitignored and untracked — don't plan work that edits them; Integration.xctestplan is credential-bearing) |
code-style.md |
editing any file — auto-format hooks reshape it on disk; pinned tool versions; editor-diagnostic lag |
.claude/docs/ carries imperative how-to-work-here detail; knowledge/ (below)
carries reference material — why/what/gotcha. Keep new content on its own side
of that line.
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 · 174 lines · 2,244 tokens per session scan A 8737e0d37740
TMDb CLAUDE.md is an instructions file published in the GitHub repository adamayoung/TMDb (177 stars, last pushed 7d ago), licensed Apache-2.0. It adds 2,244 tokens to every session, about $0.0112 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
graftcode graftcode-kotlin.instructions.md
Instructions for grft-dev/graftcode, covering graftcode — kotlin backend services, when this applies (always), authoritative docs (source of truth), golden rules and service = plain maven/gradle module (no web framework).
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).
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).