Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add chrischall/hemnet-mcp --skill hemnet-fpxgit 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/skills/chrischall/hemnet-mcp/hemnet-fpx)<a href="https://agentmods.dev/skills/chrischall/hemnet-mcp/hemnet-fpx"><img src="https://agentmods.dev/badge/skills/chrischall/hemnet-mcp/hemnet-fpx/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/skills/chrischall/hemnet-mcp/hemnet-fpx"><img src="https://agentmods.dev/badge/skills/chrischall/hemnet-mcp/hemnet-fpx.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.00091 | $0.00894 |
| Opus 5 | $0.00046 | $0.00447 |
| Sonnet 5 | $0.00018 | $0.00179 |
| Haiku 4.5 | $0.00009 | $0.00089 |
Grade A, and why
hemnet-fpx scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
managed challenge that 403s any plain `curl`/Node request. `fpx` routes the How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hemnet via fpx (no MCP)
Hemnet fronts www.hemnet.se — including /graphql — with a Cloudflare
managed challenge that 403s any plain curl/Node request. fpx routes the
request through the user's own signed-in browser tab (the Transporter
extension), which has already cleared the challenge, so the same anonymous
GraphQL query succeeds. No Hemnet login is needed — just a normal open tab.
This is the same data the hemnet_* MCP tools return (money in SEK
strings, areas in m²), reached with one CLI call instead of a running
server.
One-time setup
npm install -g @fetchproxy/cli # provides `fpx`
fpx profile add hemnet --domain hemnet.se # only the fetch capability is needed
fpx pair -p hemnet # prints a pair code → approve in Transporter
Requirements: the Transporter browser extension installed, with an open
www.hemnet.se tab, and its Chrome Site access allowing hemnet.se.
Pairing persists — after the first approval every later fpx call reuses it.
Core call
Every query is a POST of {"query": "...", "variables": {...}} to the
GraphQL endpoint. Send the body raw (no --json) so stdout is the GraphQL
JSON, ready for jq:
fpx post-json 'https://www.hemnet.se/graphql' @query.json -p hemnet \
| jq '.data'
@file reads the body from a file; a literal '{...}' string works too but
shell-quoting the embedded query is fiddly — prefer a heredoc into a file.
Ready-to-run query bodies (autocomplete, for-sale search, listing detail,
sold search) with jq recipes are in references/graphql-queries.md. Exhaustive
field lists live in the repo at src/graphql.ts — the operations here are
compact, live-verified subsets.
The one rule: resolve the location first
Hemnet searches take numeric location ids, never place names. Always
autocomplete first, take the locationId, then search:
printf '{"query":"query($q:String!,$l:Int!){autocompleteLocations(query:$q,limit:$l){hits{locationId fullName parentFullName}}}","variables":{"q":"Höllviken","l":3}}' > /tmp/q.json
fpx post-json 'https://www.hemnet.se/graphql' @/tmp/q.json -p hemnet \
| jq -r '.data.autocompleteLocations.hits[] | "\(.locationId)\t\(.fullName)"'
# 898675 Höllviken tätort
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 80 lines · 91 tokens per session scan A 5bdecd092c54
hemnet-fpx is a skill published in the GitHub repository chrischall/hemnet-mcp (1 stars, last pushed today), licensed MIT. It adds 91 tokens to every session and 894 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…