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 m-binimran/real-estate-pack --skill lead-followupgit clone --depth 1 https://github.com/m-binimran/real-estate-packWrote 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/m-binimran/real-estate-pack/lead-followup)<a href="https://agentmods.dev/skills/m-binimran/real-estate-pack/lead-followup"><img src="https://agentmods.dev/badge/skills/m-binimran/real-estate-pack/lead-followup/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/m-binimran/real-estate-pack/lead-followup"><img src="https://agentmods.dev/badge/skills/m-binimran/real-estate-pack/lead-followup.svg" alt="Reviewed on agentmods" width="80" 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.00047 | $0.00316 |
| Opus 5 | $0.00023 | $0.00158 |
| Sonnet 5 | $0.00009 | $0.00063 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
lead-followup 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 10d 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
lead-followup
Stay top-of-mind with helpful, compliant touches - not spam, not steering.
Process
- Segment by stated interest/stage (new buyer, active buyer, seller-curious, past client) - never by a protected class or inferred demographic.
- Lead with value: a relevant listing, a market stat, a useful tip - not "are you ready to buy yet?"
- Cadence: front-load early (day 0, 2, 5), then taper (weekly -> monthly). Mix channels lightly.
- Compliance: every email needs an unsubscribe and your brokerage identification (CAN-SPAM); texts need prior consent and STOP handling (TCPA). Honor opt-outs immediately.
- Personalize from their stated criteria, not assumptions about who they are.
Output
- The sequence (channel, timing, subject/preview, body) with merge fields, plus the opt-out/identification lines.
Guardrails
- No Fair Housing steering or profiling in copy or segmentation.
- Respect CAN-SPAM (unsubscribe + ID) and TCPA (consent + STOP). Don't text without consent.
- Keep lead PII out of shared/marketing files (confidentiality rule).
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.
- 10d ago First seen · 26 lines · 47 tokens per session scan A 69d6c7a68a51
lead-followup is a skill published in the GitHub repository m-binimran/real-estate-pack (2 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 316 once invoked, about $0.0002 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 skills, from other repositories
catalyst-center-readonly
Query Cisco Catalyst Center read-only — device inventory, site hierarchy, wireless, assurance health, compliance, software images, events. All 514 read-only API operations reachable through 8 grouped dispatchers. Use when asked what Catalyst Center manages, where a device sits, what its health or compliance state is…
huawei-cloud-ucs-policy-governor
Huawei Cloud UCS (Ubiquitous Cloud Native Service) policy governance and compliance management skill using hcloud CLI. Use this skill when the user wants to: (1) manage UCS policy instances - create/update/query/delete, (2) manage UCS policy definitions - query/list, (3) enable/disable policies on clusters or fleet…
cis-aws-database-5.10
Ensure Security Configurations are Reviewed Regularly.
cis-aws-compute-2.4
Ensure an Organizational EC2 Tag Policy has been Created.
cis-aws-compute-2.14
Ensure EC2 Auto Scaling Groups Propagate Tags to EC2 Instances that it launches.
ebpf-observability
Use eBPF for deep kernel-level observability — trace syscalls, network flows, and application behavior without code changes using Cilium, Tetragon, and bpftrace.