Borrowing it
Nothing to install: this file belongs to joshghal/holoscrape-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/joshghal/holoscrape-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/joshghal/holoscrape-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/joshghal/holoscrape-mcp/claude-md)<a href="https://agentmods.dev/instructions/joshghal/holoscrape-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/joshghal/holoscrape-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.01453 | $0.01453 |
| Opus 5 | $0.00727 | $0.00727 |
| Sonnet 5 | $0.00291 | $0.00291 |
| Haiku 4.5 | $0.00145 | $0.00145 |
Grade A, and why
holoscrape-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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — holoscrape-mcp (standalone MCP server)
This is the public, npm-published half of HoloScrape. The other half — the Chrome MV3
extension the server talks to — lives in the private repo joshghal/holoscrape at
~/Documents/personal/ideation/holoscrape.
Rule: index.mjs here and holoscrape/mcp/index.mjs in the extension repo must stay
byte-identical. Any change to one must be applied to the other in the same task, verified
with diff. The extension repo's test suite is what exercises this server — run npm test
over there after touching index.mjs here.
Publishing: users get this via npx -y holoscrape-mcp from the npm registry. Local edits
reach nobody until commit → push → version bump → npm publish (the user supplies the OTP).
Never publish, commit, or push without the user explicitly asking.
Communication
Explain changes in tables and bullet points, not paragraph prose.
Tool descriptions are the product, not documentation
This file is where every tool's description text lives, and those descriptions are the only thing steering the model that calls them. Write them as decision procedures for a model, not as API reference prose:
- say WHEN to reach for the tool and when NOT to (the "Best for: / Not recommended for:" shape);
- name the field to read before trusting a result (
looksLikeFurniture,distinctness,containerRows) and say what a misleading value looks like; - prefer teaching the model to choose over adding a special case to the engine. Capability goes in the code generically; the knowledge of when to use it goes in the description.
Corollary: no site-specific logic in the server or engine. Per-app facts (where an app hides its
store, how it paginates) live in the extension's providers.js descriptors as DATA. A tool that
branches on a hostname is a bug in this architecture.
Never tune a test to get green
A red test means the logic is wrong — change the logic until the ORIGINAL assertion passes. Never loosen an assertion, skip a case, soften a fixture, or special-case test input in production code. If a test genuinely asserts wrong behaviour, say so and get agreement before editing it; never quietly edit it and report "all green."
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 · 99 lines · 1,453 tokens per session scan A 354f9f8b5406
holoscrape-mcp CLAUDE.md is an instructions file published in the GitHub repository joshghal/holoscrape-mcp (0 stars, last pushed 16d ago), licensed MIT. It adds 1,453 tokens to every session, about $0.0073 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.