Borrowing it
Nothing to install: this file belongs to findmephoto/findme-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/findmephoto/findme-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/findmephoto/findme-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/findmephoto/findme-mcp/claude-md)<a href="https://agentmods.dev/instructions/findmephoto/findme-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/findmephoto/findme-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/findmephoto/findme-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/findmephoto/findme-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.00453 | $0.00453 |
| Opus 5 | $0.00227 | $0.00227 |
| Sonnet 5 | $0.00091 | $0.00091 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
findme-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.
What it actually says
findme-mcp — Project Memory
Canonical docs folder
All project docs live at /Users/seb/Claude Assistant/projects/findme-mcp/. That's the source of truth — keep new learnings there, not in this file.
| Doc | Purpose |
|---|---|
RELEASE.md |
End-to-end release runbook. Read this before doing any version bump. Covers npm + MCP Registry + findme-photo dep coordination, credential locations, race-window avoidance, verification commands. |
MCP_INFRA.md |
Architecture, endpoints, OAuth flow, secrets registry. |
TOKEN_ROTATION.md |
When/how to rotate NPM_TOKEN and FINDMEPHOTO_PAT. |
SPEC.md |
Technical spec referenced by REST API route comments. |
SETUP.md / PRD.md / NEXT_STEPS.md / TEST_CHECKLIST.md / USER_INSTALL_GUIDE.md |
Setup, requirements, launch items, manual verification, install guide. |
Quick orientation
Two transports, one tool registry (src/registry.ts):
src/index.ts— stdio (npx findme-mcp). Bidirectional → elicitation works.src/http.ts— Streamable HTTP factory. Consumed by findme.photo atapp/api/mcp/route.ts. JSON-response mode →noopElicitor, falls back toneeds_inputJSON.
Companion repo: /Users/seb/findme-photo. Pins findme-mcp version in:
package.json→"findme-mcp": "^X.Y.Z"app/api/mcp/route.ts→serverVersion: 'X.Y.Z'
Both must be bumped on every release.
The one manual step in any release
mcp-publisher login github → device-flow code requires user to authorize via browser. Everything else (npm publish, git push, Vercel deploy verification, MCP Registry publish) runs unattended with credentials already on disk.
For full procedure see /Users/seb/Claude Assistant/projects/findme-mcp/RELEASE.md.
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 · 32 lines · 453 tokens per session scan A 0029b69ad9ec
findme-mcp CLAUDE.md is an instructions file published in the GitHub repository findmephoto/findme-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 453 tokens to every session, about $0.0023 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.