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.
git 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/commands/zeropointrepo/zillow-plugin/zestimate)<a href="https://agentmods.dev/commands/zeropointrepo/zillow-plugin/zestimate"><img src="https://agentmods.dev/badge/commands/zeropointrepo/zillow-plugin/zestimate.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.00017 | $0.00258 |
| Opus 5 | $0.00009 | $0.00129 |
| Sonnet 5 | $0.00003 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
zestimate 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 7d 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.
What it actually says
Get the current Zestimate for: $ARGUMENTS
Steps:
- Identify the property from the input above (or from conversation context). If none was given, ask for a U.S. address or a zillow.com link — do not guess.
- Pick the cheapest correct tool from the
zillapiMCP server:- A
zillow.com/homedetails/...URL or a known zpid →get_zestimatewith that zpid (1 credit; the zpid is the number right before_zpidin the URL). - A street address →
lookup_property_by_address(3 credits; the full record already includes the Zestimate — do NOT also callget_zestimate).
- A
- Report: Zestimate, rent Zestimate, and — when the full record is available — tax-assessed value and last sold price for context. One line each, with a reminder that a Zestimate is an automated estimate, not an appraisal.
If the 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.
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.
- 7d ago First seen · 17 lines · 17 tokens per session scan A 27c24b22e013
zestimate is a command published in the GitHub repository ZeroPointRepo/zillow-plugin (0 stars, last pushed 14d ago), licensed MIT. It adds 17 tokens to every session and 258 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.
Other commands, from other repositories
research
Professional equity research analysis with institutional-grade formatting.
close-review
Month-end close / GL compliance check — invokes accounting-reviewer to produce TM-accounting-{slug}.md with double-entry integrity, ASC 606 revenue-recognition, period-lock, and SOX ITGC gaps.
tax-review
Tax-filing compliance check — invokes tax-reviewer to produce TM-tax-{slug}.md with MeF e-file schema, Form 8879, PTIN/Circular 230, and IRC §7216 consent gaps.
compare
Compare two or more payment providers head to head for a concrete situation — real fees on a real amount, coverage, onboarding time, and what PagoKit can actually build for each.
add
Add a second payment provider alongside an existing integration, without touching the one already running.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).