Borrowing it
Nothing to install: this file belongs to dungnotnull/Real-Estate-Title-Dispute-History-Due-Diligence-Advisor-agent-skill. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dungnotnull/Real-Estate-Title-Dispute-History-Due-Diligence-Advisor-agent-skill/main/CLAUDE.mdgit clone --depth 1 https://github.com/dungnotnull/Real-Estate-Title-Dispute-History-Due-Diligence-Advisor-agent-skillWrote 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/instructions/dungnotnull/real-estate-title-dispute-history-due-diligence-advisor-agent-skill/claude-md)<a href="https://agentmods.dev/instructions/dungnotnull/real-estate-title-dispute-history-due-diligence-advisor-agent-skill/claude-md"><img src="https://agentmods.dev/badge/instructions/dungnotnull/real-estate-title-dispute-history-due-diligence-advisor-agent-skill/claude-md/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/instructions/dungnotnull/real-estate-title-dispute-history-due-diligence-advisor-agent-skill/claude-md"><img src="https://agentmods.dev/badge/instructions/dungnotnull/real-estate-title-dispute-history-due-diligence-advisor-agent-skill/claude-md.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.00997 | $0.00997 |
| Opus 5 | $0.00498 | $0.00498 |
| Sonnet 5 | $0.00199 | $0.00199 |
| Haiku 4.5 | $0.00100 | $0.00100 |
Grade A, and why
Real-Estate-Title-Dispute-History-Due-Diligence-Advisor-agent-skill CLAUDE.md 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 12d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Operating Instructions for Real Estate Title & Dispute History Due Diligence Advisor
This file tells a future Claude instance how to think and act when this skill is triggered.
Purpose
A skill helping prospective property buyers structure a due-diligence investigation into a property's title history, encumbrances, and dispute record, grounded in established real-estate due-diligence and title-examination methodology. Explicitly disclaims that it does not replace a licensed title search, notary, or real-estate attorney, and does not access non-public records itself.
Runnable architecture
This project is a complete, production-grade agent-skill system (not just a
prompt). The canonical skill registry documentation is in SKILL.md. The
runtime lives in src/title_dd/:
- Entry point:
title_dd.run_due_diligence(request)/python -m title_dd run <request.json>. - Sub-advisors:
chain_of_title,encumbrance,dispute_history,zoning,report. - Grounding:
references/(RAG-style, loaded bytitle_dd.references.loader). - Tools:
build_checklist,lien_priority,score_advisor,assemble_report. - Hooks: lifecycle, token-budget, fabrication guardrail, disclaimer guardrail, event emission.
- LLM:
stub(offline, deterministic, default) orhttp(OpenAI-compatible) with graceful fallback. - Config:
config/default_config.json+TITLE_DD_*env vars (see.env.example). - Schemas:
assets/schemas/(input, checklist, report). - Tests:
python -m pytest(17 tests) andpython -m title_dd selftest(3 fictional scenarios).
When extending the skill, register new sub-advisors with SkillRegistry, add a
references/ grounding file, and declare any new tool in ToolRegistry.
When to trigger this skill
Trigger whenever the user's request matches this skill's domain, even if they don't use the exact keywords below — infer intent from context:
- Provide a structured title-chain examination checklist (chain of title, ownership history)
- Provide an encumbrance-and-lien checklist (mortgages, easements, liens)
- Provide a litigation/dispute-history investigation checklist (court records, boundary disputes)
- Provide a zoning/land-use compliance checklist
- Draft a structured due-diligence report template summarizing findings and open risks
- Flag which steps legally require a licensed title company, notary, or attorney
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.
- 12d ago First seen · 60 lines · 997 tokens per session scan A 4e52030faf34
Real-Estate-Title-Dispute-History-Due-Diligence-Advisor-agent-skill CLAUDE.md is an instructions file published in the GitHub repository dungnotnull/Real-Estate-Title-Dispute-History-Due-Diligence-Advisor-agent-skill (5 stars, last pushed 1mo ago), licensed MIT. It adds 997 tokens to every session, about $0.0050 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 instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).