Borrowing it
Nothing to install: this file belongs to chrischall/hemnet-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/chrischall/hemnet-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/chrischall/hemnet-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/chrischall/hemnet-mcp/claude-md)<a href="https://agentmods.dev/instructions/chrischall/hemnet-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/chrischall/hemnet-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.03192 | $0.03192 |
| Opus 5 | $0.01596 | $0.01596 |
| Sonnet 5 | $0.00638 | $0.00638 |
| Haiku 4.5 | $0.00319 | $0.00319 |
Grade A, and why
hemnet-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 2d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — hemnet-mcp
Guidance for Claude working in this repo.
TL;DR
MCP server for hemnet.se, Sweden's largest property portal. Reads active for-sale listings, sold prices (slutpriser), full listing detail, photos, and market statistics; resolves place names and street addresses; and does a local Swedish mortgage calculation. stdio transport.
Data access is an anonymous GraphQL fetch with a browser-bridge
fallback. The queries themselves need no auth — no login, no Hemnet
session — but as of 2026-07-13 Hemnet fronts the whole www.hemnet.se
zone (including /graphql) with a Cloudflare managed challenge
(cf-mitigated: challenge, _cf_chl_opt interstitial) that 403s every
non-browser client regardless of headers/User-Agent. Cloudflare
fingerprints the HTTP client itself, so no header set or replayed cookie
durably clears it — the request must ride a real browser session. So the
default transport (src/transport-fallback.ts) tries a direct anonymous
fetch first and, the moment it gets a CloudflareChallengeError,
switches to the fetchproxy bridge (src/transport-fetchproxy.ts) for
the rest of the process — a same-origin fetch inside the user's own
www.hemnet.se tab (no login needed, just a cleared Cloudflare session).
HEMNET_TRANSPORT pins the mode: direct (fail hard when walled),
fetchproxy (always bridge), auto (default fallback). When Hemnet
drops or re-scopes the wall, auto transparently rides the direct path
again. This makes hemnet-mcp a fetchproxy member like homes-mcp/redfin,
but lazily — the bridge is only built if/when the direct path is
actually walled, and the fetchproxy fleet shares port 37149
(HEMNET_WS_PORT).
Dual-purpose by design. hemnet-mcp is both (1) a standalone stdio MCP
server (the bin), and (2) an importable library (import … from 'hemnet-mcp', src/lib.ts) so the planned @chrischall/realty-meta
orchestrator in realty-mcp can consume Hemnet as one portal source. Keep
that split intact: tools depend on HemnetClient, the client returns
normalised records from src/format.ts, and nothing tool-specific leaks
into the library surface.
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.
- 2d ago Changed 4f4699492595
- 3d ago Changed · +9 lines · +176 tokens per session 60096860f545
- 7d ago First seen · 223 lines · 3,016 tokens per session scan A fc57365d08ea
hemnet-mcp CLAUDE.md is an instructions file published in the GitHub repository chrischall/hemnet-mcp (1 stars, last pushed 3d ago), licensed MIT. It adds 3,192 tokens to every session, about $0.0160 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.