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 paulieb89/property-shared --skill property-reportgit clone --depth 1 https://github.com/paulieb89/property-sharedWrote 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/paulieb89/property-shared/property-report)<a href="https://agentmods.dev/skills/paulieb89/property-shared/property-report"><img src="https://agentmods.dev/badge/skills/paulieb89/property-shared/property-report/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/paulieb89/property-shared/property-report"><img src="https://agentmods.dev/badge/skills/paulieb89/property-shared/property-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 48 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
- high System Prompt Leakage · line 197 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00092 | $0.02729 |
| Opus 5 | $0.00046 | $0.01365 |
| Sonnet 5 | $0.00018 | $0.00546 |
| Haiku 4.5 | $0.00009 | $0.00273 |
Grade A, and why
property-report 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Property Report Generator
You generate comprehensive UK property reports from a single address or postcode. You pull real data from multiple sources and present it as a clear, structured report that a property investor, estate agent, or landlord can act on.
When to Use This Skill
- "What's this property worth?"
- "Analyse this address"
- "What are the comps for [postcode]?"
- "Is this a good rental investment?"
- "Pull me a property report"
- Any request involving UK property valuation, comparison, or analysis at a known address or postcode
Not this skill: If the user wants to find properties ("find me a BTL", "search for deals in NG5"), use property-search instead.
Query Routing — Pick Your Lane
Before you start, decide which lane this query fits. Don't chain every tool by default — pick the minimum set for what was asked.
Lane A — Specific property ("what's 14 Elm St worth?", "is this property overpriced?", any time the user named a specific house or gave a street address)
Tools: search_comps (with address) → epc_lookup (with address) → get_rental → get_yield → stamp_duty → optionally rightmove_search for market context.
Output: full 8-section report.
Lane B — Area investment scan ("should I buy in NG11 9HD?", "is this a good rental area?", "I'm looking at a flat in [postcode]", vague postcode-only investment queries)
Tools: search_comps (no address — returns enriched comps with area-level EPC data) → get_rental → get_yield. Only call stamp_duty when the user gives a budget. Skip epc_lookup — the comps already have the EPC data attached to real sales.
Output: area overview. Skip the "Property Overview" section. Emphasise "Market Context" and "Yield Estimate". Prose paragraphs, not a formal 8-section report unless the user explicitly asks for one.
Lane C — Quick area stat ("typical prices in NG11 9HD?", "what EPC ratings are common here?", one-shot stat questions)
Tools: search_comps only. EPC enrichment gives ratings and floor area per transaction already. For a pure "what ratings are common?" question with no sales angle, epc_lookup (no address) returns the area summary directly — faster than comps for that narrow case.
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 · 220 lines · 92 tokens per session scan A c7546ce78952
property-report is a skill published in the GitHub repository paulieb89/property-shared (16 stars, last pushed 3d ago), licensed MIT. It adds 92 tokens to every session and 2,729 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-30.
Other skills, from other repositories
pine
Writes Pine Script v6 indicators and strategies for TradingView from natural-language descriptions. Use when the user asks Claude to write or build a Pine Script indicator, strategy, oscillator, or TradingView script, asks for a Pine v6 script, asks to convert v4/v5 Pine code to v6, or describes a trading…
second-order-thinking
Think beyond immediate consequences to understand the chain reactions of decisions. Master Howard Marks' investment framework for seeing what others miss. Use when: Strategic decisions where long-term consequences matter; Policy/rule changes that will trigger behavioral responses; Competitive moves to anticipate…
forecast-scenarios
Model best-case, worst-case, and likely revenue scenarios with sensitivity analysis for strategic planning. Use when: building financial forecasts; presenting board scenarios; planning headcount around revenue uncertainty; modeling pricing changes impact; preparing investor updates with upside/downside ranges.
commission-intelligence
Explain sales commission calculations, resolve discrepancies, and model compensation scenarios for quota planning.
pipeline-forecasting
Generate predictive pipeline forecasts with confidence intervals and scenario modeling for revenue planning.
alpha-vantage
Access real-time and historical stock market data, forex rates, cryptocurrency prices, commodities, economic indicators, and 50+ technical indicators via the Alpha Vantage API. Use when fetching stock prices (OHLCV), company fundamentals (income statement, balance sheet, cash flow), earnings, options data, market…