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 disclosure-checklistgit 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/disclosure-checklist)<a href="https://agentmods.dev/skills/m-binimran/real-estate-pack/disclosure-checklist"><img src="https://agentmods.dev/badge/skills/m-binimran/real-estate-pack/disclosure-checklist/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/disclosure-checklist"><img src="https://agentmods.dev/badge/skills/m-binimran/real-estate-pack/disclosure-checklist.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.00033 | $0.00326 |
| Opus 5 | $0.00016 | $0.00163 |
| Sonnet 5 | $0.00007 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
disclosure-checklist 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 11d 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
disclosure-checklist
Disclosures vary heavily by state - this builds the checklist and flags what to confirm locally.
Common items (confirm against YOUR state + MLS)
- Federal: Lead-Based Paint disclosure + EPA pamphlet for homes built before 1978.
- Seller property condition / TDS-type disclosure: known material defects, systems, history.
- Natural hazard / environmental: flood zone, wildfire, earthquake, etc. (state-dependent).
- Material facts: known issues affecting value/safety (deaths/stigma rules vary by state).
- HOA documents if applicable: CC&Rs, budget, fees, minutes.
- Agency disclosure and any AI/photo disclosure (virtual staging labeled).
- Local/state-specific addenda (e.g. CA TDS/NHD; transfer tax forms).
Process
- Build the list for this property, mark each delivered/acknowledged, and flag every item that depends on state law with "confirm with broker/state requirements."
Output
- A disclosure checklist: item -> required? -> delivered/acknowledged -> notes, with state-specific items flagged.
Guardrails
- This is a starting checklist, not legal advice - your state, MLS, and brokerage define the binding requirements. Confirm with your broker / attorney.
- Never advise concealing a known material defect - disclose.
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.
- 11d ago First seen · 30 lines · 33 tokens per session scan A fe21e730c8ca
disclosure-checklist is a skill published in the GitHub repository m-binimran/real-estate-pack (2 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 326 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
akf-trust-metadata
The AI native file format. EXIF for AI — stamps every file with trust scores, source provenance, and compliance metadata. Embeds into 20+ formats (DOCX, PDF, images, code). EU AI Act, SOX, HIPAA auditing.
achieving-cmmc-level-2-compliance
Prepare a defense-contractor environment for CMMC Level 2 certification: scope CUI and FCI, implement the 110 NIST SP 800-171 Rev 2 security requirements across 14 families, compute the SPRS score with the DoD Assessment Methodology, manage a compliant POA&M, and ready the organization for a C3PAO assessment. Use when…
fedramp
Expert guidance for FedRAMP certification and compliance under CR26 (FedRAMP Consolidated Rules for 2026). Use this skill whenever a user asks about FedRAMP authorization, ATO (Authority to Operate), cloud security for federal government, NIST SP 800-53 controls, CSP compliance, or any of the core FedRAMP document…
eu-cra
Expert EU Cyber Resilience Act (CRA) advisor for Regulation (EU) 2024/2847 — mandatory cybersecurity and vulnerability handling requirements for all products with digital elements (PDEs) sold in the EU. Use this skill for gap analysis, product classification (Default / Class I / Class II), conformity assessment route…
compliance-checker
Check affiliate content for FTC compliance and platform rules. Triggers on: "check my content for compliance", "FTC disclosure check", "is this legal", "review for compliance", "check affiliate disclosure", "am I FTC compliant", "audit my content", "compliance review", "legal check", "platform rules check", "check…
app-store-preflight-compliance
Pre-submission compliance scanner workflow for Apple App Store apps. Use when reviewing iOS, macOS, tvOS, watchOS, or visionOS projects (Swift, Objective-C, React Native, Expo) for App Store rejection risks, submission readiness, privacy compliance, or guideline violations.