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 ZeroPointRepo/zillow-plugin --skill zillowgit clone --depth 1 https://github.com/ZeroPointRepo/zillow-pluginWrote 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/zeropointrepo/zillow-plugin/zillow)<a href="https://agentmods.dev/skills/zeropointrepo/zillow-plugin/zillow"><img src="https://agentmods.dev/badge/skills/zeropointrepo/zillow-plugin/zillow/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/zeropointrepo/zillow-plugin/zillow"><img src="https://agentmods.dev/badge/skills/zeropointrepo/zillow-plugin/zillow.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.00083 | $0.01039 |
| Opus 5 | $0.00042 | $0.00519 |
| Sonnet 5 | $0.00017 | $0.00208 |
| Haiku 4.5 | $0.00008 | $0.00104 |
Grade A, and why
zillow 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 9d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zillow property data (Zillapi)
This plugin bundles the hosted zillapi MCP server (https://api.zillapi.com/mcp). Its four tools are the only data path — never scrape zillow.com and never call the REST API directly from this skill.
Authentication is automatic. The MCP server uses OAuth 2.1: the first tool call prompts the user to sign in (or create a free account — 100 credits, no card). There is no API key to configure. If tools fail with an auth error, tell the user to complete the sign-in prompt in their client, or re-enable the zillapi MCP server in settings.
When to use
DO use when the user:
- Asks what a home is worth, its Zestimate, rent Zestimate, taxes, or last sale →
get_zestimate(if you have a zpid) orlookup_property_by_address - Gives a U.S. address and asks about the property, its photos, schools, price history, or listing agent →
lookup_property_by_address(one call returns all of it) - Pastes a
zillow.com/homedetails/...link → extract the zpid from the URL (the number before_zpid) and uselookup_property_by_zpid - Asks to find homes matching criteria (area, price, beds, for sale / for rent / sold) →
search_listings - Asks for comps → look up the subject property, then
search_listingswithstatus: "sold"in a small bounding box around it
Do NOT use when:
- An address appears incidentally (signatures, unrelated documents)
- The user discusses real estate abstractly without asking for data on a specific property or search
- The user hasn't signaled they want a lookup — tool calls cost credits; when intent is ambiguous, confirm first
Tools (exact MCP surface)
lookup_property_by_address — 3 credits
address(string, required): full street address with city, state, ZIP — e.g."17 Zelma Dr, Greenville, SC 29617". Partial addresses ≥6 chars usually resolve.- Returns the full record (300+ fields): price, Zestimate, rent Zestimate, tax history, price history, photos, schools, agent contact, lat/lon, zpid.
- This already contains everything — don't follow it with
get_zestimatefor the same property.
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.
- 9d ago First seen · 59 lines · 83 tokens per session scan A a142cfc13bf8
zillow is a skill published in the GitHub repository ZeroPointRepo/zillow-plugin (0 stars, last pushed 16d ago), licensed MIT. It adds 83 tokens to every session and 1,039 once invoked, about $0.0004 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
domscribe
Work with Domscribe — the pixel-to-code bridge. Use when setting up, initializing, or configuring Domscribe for a project, OR when editing or modifying UI components (React, Vue, Next.js, Nuxt), implementing features from captured UI annotations, querying runtime context for source locations, exploring component…
wavedash
Use when building, integrating, testing, uploading, publishing, or preparing a browser game for Wavedash, including CLI setup, Wavedash SDK features, multiplayer, achievements, leaderboards, cloud saves, player identity, user-generated content, store metadata, monetization, and content guidelines.
proctor
Honest-completion ruleset for changes that touch tests or the code they cover. Use before deleting, skipping, renaming, or rewriting a test, before weakening an assertion, and before hardcoding or stubbing an implementation to make a test pass. Also covers what to do when a test looks genuinely wrong.
signals-scout-csp-violations
Signals scout for Content Security Policy violations. Watches $cspviolation events for blocked-URL clusters, per-directive bursts, post-deploy regressions, and suspicious third- party domains.
signals-scout-data-warehouse
Signals scout for warehouse imports. Watches external data sources, sync schemas, webhook push channels, and materialized views for failures, silent staleness, and row-volume cliffs, and suggests materialization candidates from recurring query-log hot spots.
signals-scout-web-vitals
Signals scout for Core Web Vitals ($webvitals). Watches each page's p75 LCP / INP / CLS / FCP against Google's thresholds and its own history — poor-band pages, band crossings, sharp regressions — and dates each regression against deploys and flag rollouts.