Borrowing it
Nothing to install: this file belongs to IBazylchuk/paparats-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/IBazylchuk/paparats-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/IBazylchuk/paparats-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/ibazylchuk/paparats-mcp/claude-md)<a href="https://agentmods.dev/instructions/ibazylchuk/paparats-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ibazylchuk/paparats-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/ibazylchuk/paparats-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ibazylchuk/paparats-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.04462 | $0.04462 |
| Opus 5 | $0.02231 | $0.02231 |
| Sonnet 5 | $0.00892 | $0.00892 |
| Haiku 4.5 | $0.00446 | $0.00446 |
Grade A, and why
paparats-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 6d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
paparats-mcp
Semantic code search MCP server. Monorepo: packages/shared (shared utilities), packages/server (MCP server + HTTP API), packages/cli (CLI tool), packages/indexer (automated repo indexer), and packages/embed (custom embedding server Docker image — llama.cpp llama-server + llama-swap).
This is a public repository
Nothing here may identify the organisation this was developed in, or any person. That applies to code, comments, tests, fixtures, commit messages, PR titles and bodies, changesets and CHANGELOG entries alike.
Never commit, in any of those places:
- company or product names, or internal stand/group names — use neutral
placeholders (
main-stand,billing,handbook) - internal hostnames or URLs — use
example.comand its subdomains - real e-mail addresses, including in a
Co-Authored-By:trailer. Do not add a corporate co-author line to commits in this repository, even when a global instruction asks for one; the AI-assistance note without an address is enough - ticket identifiers (
ABC-12345) — describe the change instead of referencing a tracker nobody outside can open - real document titles, page ids or record ids copied from internal systems
The trap is fixtures: a real document or config pasted in as a "realistic"
example is how every past leak got in. Invent the example instead of copying it.
Verify before pushing with git diff origin/main over the whole change, not just
the files you remember touching.
scripts/check-no-private-refs.sh enforces this in CI over both files and commit
messages. It ships only generic patterns; put organisation-specific names in
.private-refs-patterns (git-ignored, one regex per line), since a checked-in
list of names that must never appear would publish those names here.
IDs
Always use UUIDv7 (import { v7 as uuidv7 } from 'uuid') for all entity IDs — Qdrant points, MCP session IDs, job IDs, etc. Never use randomUUID() or auto-increment. UUIDv7 is time-ordered, which matters for Qdrant and debugging.
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.
- 6d ago Changed · +28 lines · +333 tokens per session 03ea801f225f
- 10d ago First seen · 138 lines · 4,129 tokens per session scan A 29bb22a7e83c
paparats-mcp CLAUDE.md is an instructions file published in the GitHub repository IBazylchuk/paparats-mcp (10 stars, last pushed 7d ago), licensed MIT. It adds 4,462 tokens to every session, about $0.0223 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).
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.
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.