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/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/commands/m-binimran/real-estate-pack/listing-description)<a href="https://agentmods.dev/commands/m-binimran/real-estate-pack/listing-description"><img src="https://agentmods.dev/badge/commands/m-binimran/real-estate-pack/listing-description.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.00034 | $0.00085 |
| Opus 5 | $0.00017 | $0.00043 |
| Sonnet 5 | $0.00007 | $0.00017 |
| Haiku 4.5 | $0.00003 | $0.00009 |
Grade A, and why
listing-description 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 8d 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
/listing-description $ARGUMENTS
Use the listing-description skill for this request: $ARGUMENTS
If no details were provided, ask for what the skill needs first, then follow the skill's process exactly.
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.
- 8d ago First seen · 10 lines · 34 tokens per session scan A 745e31be7b7c
listing-description is a command published in the GitHub repository m-binimran/real-estate-pack (2 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 85 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 commands, from other repositories
onboard-interactive
Interactive customer onboarding with Step 0 independent verification (dialog-based, 17 stagegates).
monitor
AML transaction monitoring and suspicious activity reporting.
overlay-apply
Apply NIST 800-53 overlays (FedRAMP, DoD, Privacy, etc.) to existing baselines.
pillar-guidance
Deep dive guidance on DORA's 5 pillars and implementation requirements.
dpia
Data Protection Impact Assessment (DPIA) guidance and execution.
profile-select
Determine appropriate Canadian classification level for your data.