Borrowing it
Nothing to install: this file belongs to Nokke32/pp-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/Nokke32/pp-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/Nokke32/pp-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/nokke32/pp-mcp/claude-md)<a href="https://agentmods.dev/instructions/nokke32/pp-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/nokke32/pp-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.02885 | $0.02885 |
| Opus 5 | $0.01443 | $0.01443 |
| Sonnet 5 | $0.00577 | $0.00577 |
| Haiku 4.5 | $0.00288 | $0.00288 |
Grade A, and why
pp-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 7d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Hinweise für Claude Code beim Arbeiten in diesem Repository.
Überblick
pp-mcp ist ein read-only MCP-Server, der Konten- und Depotdaten aus einer oder
mehreren Portfolio-Performance-.portfolio-Dateien gefiltert bereitstellt (für Reports).
Ein einzelner Python-Prozess, nur MCP – keine Web-UI, keine Datenbank, keine Auth
(außer optionalem Bearer-Token). Tool-Beschreibungen, Docstrings und Kommentare in
src/mcp_server.py sind auf Englisch (öffentlicher MCP-Server, internationale Nutzer/
LLMs). Diese CLAUDE.md und Commit-Messages bleiben auf Deutsch (Arbeitssprache des Maintainers).
pp-mcp ist als einzige Quelle der Wahrheit für Portfolio-Performance-Daten
gedacht: andere Anwendungen (z.B. DividendenTracker, ein künftiges Analyse-Dashboard)
sollen ausschließlich über diesen Server auf .portfolio-Dateien zugreifen und sie
nicht selbst parsen. Produktivbetrieb: NAS im lokalen Netz, intern im Docker-Netz
(nicht öffentlich exponiert, außer über einen Reverse-Proxy unter einer festen
internen Domain), zusätzlich per MCP_AUTH_TOKEN geschützt.
Dokumentation: Seit 2026-08-14 ist die ausführliche Doku (Installation,
KI-Tool-Konfiguration, Beispiel-Prompts, vollständige Tool-Referenz, Beispiel-Skripte)
im Wiki, nicht mehr in der README. Zwei gespiegelte Wikis: Gitea (primäre Quelle,
intern gehostet, lokaler Klon unter ~/Coding/MCP/pp-mcp.wiki) und GitHub
(https://github.com/Nokke32/pp-mcp/wiki, Branch master statt main). README.md/
README_de.md sind auf ein Minimum reduziert (Kurzbeschreibung, Quick-Start, Begriffe,
Struktur) und verlinken je nach Remote auf das jeweils passende Wiki (Gitea ist nur
intern erreichbar, daher zwei unterschiedliche Link-Ziele in den sonst identischen
READMEs).
Betrieb & Entwicklung
Gedacht für Docker, läuft aber auch lokal. docker-compose.yml ist der
Multi-Source-Produktivbetrieb (NAS im lokalen Netz, MCP_AUTH_TOKEN Pflicht);
docker-compose.dev.yml der einfache lokale Single-Source-Betrieb
(docker-compose -f docker-compose.dev.yml up -d --build):
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.
- 7d ago First seen · 155 lines · 2,885 tokens per session scan A fc0ec9dddf27
pp-mcp CLAUDE.md is an instructions file published in the GitHub repository Nokke32/pp-mcp (6 stars, last pushed 23d ago), licensed MIT. It adds 2,885 tokens to every session, about $0.0144 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).
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).
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.