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/offer-analysis)<a href="https://agentmods.dev/commands/m-binimran/real-estate-pack/offer-analysis"><img src="https://agentmods.dev/badge/commands/m-binimran/real-estate-pack/offer-analysis.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.00032 | $0.00083 |
| Opus 5 | $0.00016 | $0.00042 |
| Sonnet 5 | $0.00006 | $0.00017 |
| Haiku 4.5 | $0.00003 | $0.00008 |
Grade A, and why
offer-analysis 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 7d 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
/offer-analysis $ARGUMENTS
Use the offer-analysis 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.
- 7d ago First seen · 10 lines · 32 tokens per session scan A a4b79f9ac9bd
offer-analysis is a command published in the GitHub repository m-binimran/real-estate-pack (2 stars, last pushed 2mo ago), licensed MIT. It adds 32 tokens to every session and 83 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
monitor
AML transaction monitoring and suspicious activity reporting.
risk
Risk reassessment with updated due diligence.
screen
Comprehensive sanctions and PEP screening.
air-gapped-helm-handover
Run a CECL workflow on a loopback-only Helm daemon, hit the consent-tier boundary at evidence export, and cross-check the kernel against the public worker.
signed-policy-agentic-commerce
Run an agentic commerce chain under a signed Work Mandate, trip the escalation gate on purpose, and replay the gates on the ledger.
zero-egress-emir-proof
Run four EMIR Refit validators inside the browser tab, pack and anchor only the hashes, and hand a supervisor the re-verification recipe.