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 agentmods add commands/zeropointrepo/zillow-plugin/propertygit 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/property)<a href="https://agentmods.dev/commands/zeropointrepo/zillow-plugin/property"><img src="https://agentmods.dev/badge/commands/zeropointrepo/zillow-plugin/property.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.00027 | $0.00282 |
| Opus 5 | $0.00014 | $0.00141 |
| Sonnet 5 | $0.00005 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
property 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 5d 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
Pull the full Zillow property record 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 → extract the zpid (the number right before_zpid) and calllookup_property_by_zpid(1 credit). - A bare zpid →
lookup_property_by_zpid(1 credit). - A street address →
lookup_property_by_address(3 credits).
- A
- Present a concise summary: address, status, price, beds/baths/sqft, year built, Zestimate + rent Zestimate, tax-assessed value, last sale (date + price), schools with ratings, and listing agent if active. Offer to go deeper (full price history, photos) on request rather than dumping everything.
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.
- 5d ago First seen · 18 lines · 27 tokens per session scan A ce44ed27dc9c
property is a command published in the GitHub repository ZeroPointRepo/zillow-plugin (0 stars, last pushed 12d ago), licensed MIT. It adds 27 tokens to every session and 282 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
check
Run proctor against the current changes and report what it found.
setup
Set up proctor in this repository: the git pre-commit hook, plus the ruleset for every agent in use.
posthog:llma-cc-ingest
Manually send a Claude Code session log to PostHog LLM Analytics.
posthog:llma-cc-setup
Set up PostHog LLM Analytics to capture Claude Code sessions.
posthog:llma-cc-status
Check if Claude Code sessions are being sent to PostHog LLM Analytics.
init
Install the formatters this repository needs, with every command visible before it runs.