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/onehome-mcp --skill onehome-fpxgit clone --depth 1 https://github.com/chrischall/onehome-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/onehome-mcp/onehome-fpx)<a href="https://agentmods.dev/skills/chrischall/onehome-mcp/onehome-fpx"><img src="https://agentmods.dev/badge/skills/chrischall/onehome-mcp/onehome-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/onehome-mcp/onehome-fpx"><img src="https://agentmods.dev/badge/skills/chrischall/onehome-mcp/onehome-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.00108 | $0.01595 |
| Opus 5 | $0.00054 | $0.00797 |
| Sonnet 5 | $0.00022 | $0.00319 |
| Haiku 4.5 | $0.00011 | $0.00160 |
Grade A, and why
onehome-fpx 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 12d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OneHome via fpx (no MCP)
OneHome is a CoreLogic product: buyers reach it through a private
"magic-link" URL their real-estate agent emailed
(https://portal.onehome.com/en-US/properties/map?token=eyJ...). It's an
Angular SPA backed by one GraphQL API at services.onehome.com/graphql
(plus a couple of REST endpoints), authenticated with
Authorization: Bearer <sessionToken>. There's no anti-bot wall on
services.onehome.com — the gate is purely the per-user bearer — so fpx
is used here to reach the token itself (either by exchanging the magic
link, or by capturing it from a live tab), then to fire the actual GraphQL
calls through the same signed-in tab.
This is the same data the onehome_* MCP tools return, reached with CLI
calls instead of a running server. See src/queries.ts and src/auth.ts
in the repo for the live-verified source of every shape below.
One-time setup
npm install -g @fetchproxy/cli # provides `fpx`
fpx profile add onehome --domain onehome.com # covers portal.* and services.*
fpx profile declare onehome \
--capture-header [email protected]/graphql # needed for Path B below
fpx pair -p onehome # prints a pair code → approve in Transporter
Requirements: the Transporter browser extension installed and paired,
its Chrome Site access allowing onehome.com, and (for Path B) an open
portal.onehome.com tab signed in to the share you want to read.
Getting a bearer token (two paths)
Path A — you have the magic-link URL (from the agent's email). The
?token= value is an email-token, not a bearer — exchange it once via
the same checkToken bootstrap the Angular app runs on load. This also
hands back the consumer's scope (groupID, savedSearchID, agentID,
contactID, mlsID), so you don't have to guess group_id later:
LINK='https://portal.onehome.com/en-US/properties/map?token=eyJ...'
EMAIL_TOKEN=$(echo "$LINK" | sed -n 's/.*[?&]token=\([^&]*\).*/\1/p')
printf '{"emailToken":"%s"}' "$EMAIL_TOKEN" > /tmp/checktoken-body.json
fpx post-json 'https://services.onehome.com/api/authentication/checkToken' \
@/tmp/checktoken-body.json -p onehome \
-H 'Origin: https://portal.onehome.com' -H 'Referer: https://portal.onehome.com/' \
| tee /tmp/checktoken.json | jq '{groupID,savedSearchID,agentID,contactID,mlsID,email}'
TOKEN="Bearer $(jq -r '.sessionToken' /tmp/checktoken.json)"
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.
- 12d ago First seen · 127 lines · 108 tokens per session scan A a117de2c161f
onehome-fpx is a skill published in the GitHub repository chrischall/onehome-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 108 tokens to every session and 1,595 once invoked, about $0.0005 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 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…