comps

comps is a command for coding agents from ZeroPointRepo/zillow-plugin. It costs 20 tokens per session (363 once invoked), scanned A, original, MIT.

A command for finding recently sold homes similar to a given U.S. property. Comparable sales, often called “comps,” help estimate what a home may be worth by comparing nearby sales.

In plain words
What is it for?
Find a subject property, gather nearby sold homes, filter out poor matches, and compare the resulting estimate with the Zestimate or asking price.
Why use it?
It turns scattered sold-listing data into a quick value estimate based on price per square foot.

Command

Part of the zillow plugin — 1 skill, 4 commands, 1 MCP server shipped together

Install

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.

agentmods
npx agentmods add commands/zeropointrepo/zillow-plugin/comps
Clone the repo
git clone --depth 1 https://github.com/ZeroPointRepo/zillow-plugin

Or install zillow, the plugin that ships this one along with the rest of its 1 skill, 4 commands, 1 MCP server.

Wrote 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.

agentmods badge for comps

README.md
[![agentmods](https://agentmods.dev/badge/commands/zeropointrepo/zillow-plugin/comps.svg)](https://agentmods.dev/commands/zeropointrepo/zillow-plugin/comps)
Your own site
<a href="https://agentmods.dev/commands/zeropointrepo/zillow-plugin/comps"><img src="https://agentmods.dev/badge/commands/zeropointrepo/zillow-plugin/comps.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 363 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00363
Opus 5 $0.00010 $0.00181
Sonnet 5 $0.00004 $0.00073
Haiku 4.5 $0.00002 $0.00036

Measured 3d ago against content hash 899e34a7b2b0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

comps 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 3d 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.

commands/comps.md · 17 lines

What it actually says

Run sold comps for the subject property: $ARGUMENTS

Steps (uses the zillapi MCP server; ~10–15 credits total for a normal run):

  1. Identify the subject property from the input above. If none was given, ask for a U.S. address or zillow.com link — do not guess.
  2. Pull the subject's full record — lookup_property_by_zpid if you have a zpid from a Zillow URL (1 credit), otherwise lookup_property_by_address (3 credits). Note its lat/lon, beds, sqft, and Zestimate.
  3. Call search_listings with status: "sold", a tight bounding box around the subject's lat/lon (±0.01–0.02°, roughly a 1–2 km radius), and beds_min one below the subject's bedroom count. Each result costs 1 credit, so keep the box tight; widen only if fewer than 3 comps come back.
  4. Build the comp table: address, sold price, beds/baths, sqft, $/sqft, distance from subject. Drop obvious non-comparables (wrong home type, sqft off by more than ~40%).
  5. Conclude with: median $/sqft of the comps × subject sqft = indicated value, shown next to the Zestimate and (if listed) the asking price. Note this is an estimate from public data, not an appraisal.

If a tool call fails with an authentication error, tell the user to complete the Zillapi OAuth sign-in prompt (free account, 100 credits, no card) and retry.

Changes

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.

  1. 3d ago First seen · 17 lines · 20 tokens per session scan A 899e34a7b2b0

Subscribe to this mod's changes

comps is a command published in the GitHub repository ZeroPointRepo/zillow-plugin (0 stars, last pushed 10d ago), licensed MIT. It adds 20 tokens to every session and 363 once invoked, about $0.0001 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.