Borrowing it
Nothing to install: this file belongs to hydrolix/mcp-hydrolix. 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/hydrolix/mcp-hydrolix/main/CLAUDE.mdgit clone --depth 1 https://github.com/hydrolix/mcp-hydrolixWrote 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/hydrolix/mcp-hydrolix/claude-md)<a href="https://agentmods.dev/instructions/hydrolix/mcp-hydrolix/claude-md"><img src="https://agentmods.dev/badge/instructions/hydrolix/mcp-hydrolix/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.00301 | $0.00301 |
| Opus 5 | $0.00151 | $0.00151 |
| Sonnet 5 | $0.00060 | $0.00060 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
mcp-hydrolix 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.
What it actually says
Claude project rules — mcp-hydrolix
PRs MUST target hydrolix/mcp-hydrolix
This repository is a fork of ClickHouse/mcp-clickhouse. Because of that, gh pr create without an explicit --repo flag defaults to opening a PR against
the upstream parent (ClickHouse/mcp-clickhouse), not this repo. That is
never what we want.
Rule: every gh pr create invocation in this repo MUST include
--repo hydrolix/mcp-hydrolix explicitly. Never open a PR against
ClickHouse/mcp-clickhouse.
This rule applies in every permission mode — default, auto, acceptEdits,
bypassPermissions, anything else. A PreToolUse Bash hook at
.claude/hooks/block-clickhouse-pr.py enforces it programmatically (exit code
2 = hard block), and .claude/settings.json carries deny rules as a second
layer. Do not disable, weaken, or work around these guards.
Asking before opening PRs
Opening a pull request is a shared-state action (visible to others, hard to
undo cleanly). Do not run gh pr create unless the user has explicitly asked
for a PR in this turn. Committing locally and pushing to a branch is fine when
the user asks; opening the PR is a separate authorization.
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 · 26 lines · 301 tokens per session scan A ebcdde59f224
mcp-hydrolix CLAUDE.md is an instructions file published in the GitHub repository hydrolix/mcp-hydrolix (11 stars, last pushed 11d ago), licensed Apache-2.0. It adds 301 tokens to every session, about $0.0015 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
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.