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 agentmods add skills/datasift-ty-personal/siftstack/deep-prospectingnpx skills add DataSift-Ty-Personal/SiftStack --skill deep-prospectinggit clone --depth 1 https://github.com/DataSift-Ty-Personal/SiftStackWrote 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/datasift-ty-personal/siftstack/deep-prospecting)<a href="https://agentmods.dev/skills/datasift-ty-personal/siftstack/deep-prospecting"><img src="https://agentmods.dev/badge/skills/datasift-ty-personal/siftstack/deep-prospecting.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 | $0.00155 | $0.09679 |
| Opus 5 | $0.00077 | $0.04840 |
| Sonnet 5 | $0.00031 | $0.01936 |
| Haiku 4.5 | $0.00015 | $0.00968 |
Grade A, and why
deep-prospecting 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 3d 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.
This is a copy
88% identical to deep-prospecting-v4 — 72 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 727 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Prospecting
Deep prospecting is the process for identifying and verifying the heirs/decision-makers (owner/heir/executor) behind a distress lead, and determining who must actually sign for the property to sell. Core philosophy: "When everyone hits a wall, we bring a shovel."
Two Paths - Pick API-First
| Path | When | Reliability | Cost/record |
|---|---|---|---|
| Primary: API-Based Heir Resolution (recommended) | You have Enformion/Endato + Trestle API access | HIGH - heir set comes from the provider's relationship graph; deterministic; nothing inferred | ~$2.30-3.00 |
| Fallback: 3-Site Browser Waterfall | No API access, or API returns thin data | MEDIUM - manual assembly from obituaries/people-search sites; slower; hallucination risk | $0-0.15 + your time |
Use the Primary Path below first. It replaces hours of manual obituary and genealogy hunting with a handful of API calls and produces a grounded heir set, a signing analysis, and scored phones. Drop to the browser waterfall only when the API can't resolve a record.
Grounding rule (both paths): every name, address, phone, and relationship must come from a source you actually retrieved (an API response or a page you read). Never infer or fabricate an heir. Surface conflicts; do not resolve them by guessing.
When to Use This Skill
- Skip trace returned no usable phone numbers
- Called 3+ attempts with no contact
- Vacant mailing address discovered
- Return mail (bad address)
- Probate cases (often only docket number available)
- Entity/LLC ownership (need actual decision-maker)
- Conflicting owner/address information in public records
Input Requirements
User provides any combination of:
- Property address
- Owner name (full or partial)
- Filing/docket number
- Probate case information
- Foreclosure notice details
- Any distress record data
Workflow Overview
For a deceased owner with API access, go straight to the Primary Path: API-Based Heir Resolution (Steps A-E) below, then produce the signing analysis - it covers identification, family tree, signers, and scored phones in a few API calls. The numbered flow below is the manual/fallback sequence and the deeper research levels.
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.
- 3d ago First seen · 727 lines · 155 tokens per session scan A e535c928c097
deep-prospecting is a skill published in the GitHub repository DataSift-Ty-Personal/SiftStack (21 stars, last pushed 6d ago), licensed MIT. It adds 155 tokens to every session and 9,679 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to deep-prospecting-v4, differing in 72 lines, and is treated as a copy.
Other skills, from other repositories
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
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…
build-audit-logs
Build or review audit trails in TypeScript/JavaScript apps using evlog (pipelines, typed actions, denials, retention, compliance-style reviews). For application code, not for extending the evlog package.
nda-review
Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…
disclosure
Drive responsible disclosure of a proven finding to a CVE. Package the report, find the vendor contact, report privately, coordinate a timeline, request the CVE (vendor CNA / GitHub / MITRE), and publish an advisory. Closes the research loop. Triggers - "disclose", "request a cve", "report this to the vendor".