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 avelikiy/great_cto --skill vertical-real-estategit clone --depth 1 https://github.com/avelikiy/great_ctoWrote 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/avelikiy/great_cto/vertical-real-estate)<a href="https://agentmods.dev/skills/avelikiy/great_cto/vertical-real-estate"><img src="https://agentmods.dev/badge/skills/avelikiy/great_cto/vertical-real-estate/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/avelikiy/great_cto/vertical-real-estate"><img src="https://agentmods.dev/badge/skills/avelikiy/great_cto/vertical-real-estate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 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 System Prompt Leakage · line 42 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.
- high System Prompt Leakage · line 76 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.
- high System Prompt Leakage · line 119 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.
- high System Prompt Leakage · line 139 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.00099 | $0.02352 |
| Opus 5 | $0.00049 | $0.01176 |
| Sonnet 5 | $0.00020 | $0.00470 |
| Haiku 4.5 | $0.00010 | $0.00235 |
Grade A, and why
vertical-real-estate 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vertical: residential real estate — don't spec it naively
Real estate looks like generic CRUD (a listing is a record, a lead is a contact, a deal is a checklist). It isn't. The domain has hard-won structure — MLS quirks, status lifecycles, months-long sales cycles, agent-vs-brokerage data boundaries — that a naive build ignores and then rebuilds. This skill front-loads that structure so the spec is right the first time.
Incumbents to know (and what they own): Lone Wolf / Propertybase (brokerage CRM + back office), Follow Up Boss (lead-to-close CRM, the nurture gold standard), CINC (lead-gen
- CRM), Top Producer (legacy CRM), kvCORE / BoldTrail (all-in-one platform). They are expensive, broad, and switching-cost-heavy — which is why the wedge matters (see per-product).
1. Domain vocabulary (use these terms in the spec)
- MLS (Multiple Listing Service) — regional database of listings; there are ~500+ MLSs in the US, each its own system, login, and field set. There is no single national MLS.
- IDX (Internet Data Exchange) — the rules + feed that let a brokerage display other brokers' MLS listings on its own site. Governed by per-MLS display/redistribution rules.
- RESO — the standards body. RESO Web API (modern REST/OData feed) and RESO Data Dictionary (canonical field names) are the standard — but adoption and cleanliness vary per MLS. "RESO-compliant" still means per-MLS quirks.
- Listing status — lifecycle, not a flag:
active → pending / contingent → closed(pluscoming soon,active under contract,withdrawn,expired,sold). Status drives display rules and downstream automation. - Buyer agent vs seller (listing) agent — opposite sides of a transaction; data and permissions differ. A contact can be a buyer lead and later a seller.
- Brokerage vs agent — the brokerage holds the license and (often) the data; the agent is the user. Commission split is how the deal's commission divides brokerage↔agent.
- Escrow / settlement / closing — the funded close; contingencies (inspection, financing, appraisal) are conditions that must clear first, each with a deadline.
- Transaction coordinator (TC) — the person who shepherds a deal from accepted-offer to close: chasing docs, signatures, and deadlines. Often done in Dotloop / Excel today.
- CMA (Comparative Market Analysis) — comp-based price estimate an agent gives a seller.
- Lead-to-close funnel — capture → nurture → active → under-contract → closed; months long.
- Syndication portals — Zillow, Realtor.com, Redfin, Trulia, etc.; a listing is pushed (syndicated) to many; our copy is one of many downstream copies.
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 · 141 lines · 99 tokens per session scan A 5eb4f9abedf3
vertical-real-estate is a skill published in the GitHub repository avelikiy/great_cto (93 stars, last pushed yesterday), licensed MIT. It adds 99 tokens to every session and 2,352 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-09-03.
Other skills, from other repositories
spec-drift
Standalone plan-vs-code audit on any branch: runs /ship Step 8's plan-completion section from disk (hash-pinned) against an explicit plan and base. Report, JSON, exit code. Never edits code.
third-lens-review
After Claude self-pitfall + Codex on a ship-worthy/architecture/RT/security/contract change: run a third external model house (distant training distribution → different blind spots) on the patched artifact, then adversarial synthesis.
quality-review
After a PRD, spec, or plan, before implementation: hunt perceived-quality pitfalls (silent failures, missing loading/empty states, error recovery, state drift) that make a product feel cheap. Complements pitfall-verification.
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
triage
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.