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 tonydzi/second-brain-starter-kit --skill dig-through-data-brokersgit clone --depth 1 https://github.com/tonydzi/second-brain-starter-kitWrote 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/tonydzi/second-brain-starter-kit/dig-through-data-brokers)<a href="https://agentmods.dev/skills/tonydzi/second-brain-starter-kit/dig-through-data-brokers"><img src="https://agentmods.dev/badge/skills/tonydzi/second-brain-starter-kit/dig-through-data-brokers/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/tonydzi/second-brain-starter-kit/dig-through-data-brokers"><img src="https://agentmods.dev/badge/skills/tonydzi/second-brain-starter-kit/dig-through-data-brokers.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.00073 | $0.03410 |
| Opus 5.5 | $0.00029 | $0.01364 |
| Sonnet 5.5 | $0.00015 | $0.00682 |
| Haiku 4.5 | $0.00007 | $0.00341 |
Grade A, and why
dig-through-data-brokers 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 6d 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
98% identical to dig-through-data-brokers — 24 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dig through data brokers
People-search sites resell a blend of public records, marketing data, and self-reported data. They are fast, cheap lead generators and terrible evidence. The one rule that matters: a broker record is a lead, never a fact. Confirm every field you intend to use against the primary source the broker got it from — and if you cannot identify that primary source, do not use the field.
What these services actually are
Three input streams, blended and sold:
- Public records — property deeds, court filings, business registrations, voter files where public, professional licences, bankruptcy, marriage and divorce. Authoritative at origin; the broker's copy is a stale transcription.
- Marketing and commercial data — warranty cards, loyalty programmes, subscriptions, credit-header data, online forms, ad exchanges. Never verified, often inferred, frequently household-level rather than person-level.
- Self-reported and scraped — profiles, résumés, forum posts, and whatever the broker's own users typed in.
They also buy from each other, constantly. That is the most important structural fact about the category: one wrong record propagates across every brand, and cross-checking five brokers gives you five copies of one error wearing five hats. Apparent corroboration across brokers is worth close to nothing.
Why the data is wrong
- Address history is append-only in practice. Brokers add addresses and rarely retire them, so a "current address" is often several moves old.
- Household merging. Two people at one address, or two people with the same name in one metro area, get fused into one profile. Same-name relatives — father and son, cousins named for the same grandparent — merge constantly.
- Relatives are inferred, not recorded. "Relatives" and "associates" lists are usually address-co-occurrence: former roommates, landlords, and the previous occupant show up as family.
- Age is derived. Often from a birth year in a credit header or a voter file, and often off by a year or displayed as a band.
- Phone data ages fastest. Number portability and prepaid churn mean carrier
and line-type attributions decay quickly — see
whose-number-is-this. - Corrections do not propagate. Getting one broker to fix a record does not fix the upstream source or the six downstream buyers.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago Changed 05aed8732ab6
- 19d ago Changed · -1 lines 4940ea2cdf98
- 24d ago Changed · +13 lines 761d269a659d
- 1mo ago First seen · 250 lines · 73 tokens per session scan A edfa5b06471f
dig-through-data-brokers is a skill published in the GitHub repository tonydzi/second-brain-starter-kit (12 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 3,410 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to dig-through-data-brokers, differing in 24 lines, and is treated as a copy.
Other skills, from other repositories
compliance-check
Run a content draft against the compliance knowledge base in brain/compliance/ and return PASS or FAIL with exact concerns. Use on every draft before it reaches output/drafts/ or Mai Marketing Machine, and whenever the owner says "compliance check", "is this compliant", or "check this post". No draft proceeds without…
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
wiki
Initialize, adopt, and route work for a separate Obsidian knowledge vault through the portable claude-obsidian core. Use for vault setup, scaffolding, workspace selection, cross-project configuration, or choosing the correct wiki sub-skill. Triggers: /wiki, set up wiki, scaffold vault, create knowledge base, adopt…
defuddle
Plan optional Defuddle extraction and retain already available local source files through reviewed filesystem capture. Use for defuddle, clean this URL, strip page clutter, readable Markdown from a web page, or preparing a web source for later wiki ingestion. Network extraction remains unavailable until an enforcing…
wiki-fold
Create a bounded, extractive, structurally idempotent rollup of recent Obsidian wiki log entries, with dry-run preview by default and one optional transaction apply. Use for manual log compression without modifying child pages. Triggers: fold the log, run a fold, run wiki-fold, log rollup, roll up log entries, commit…
wiki-mode
Read or configure the vault filing methodology and suggest destinations for planned knowledge creation under Generic, LYT, PARA, or Zettelkasten. Use for wiki mode, methodology mode, what is my vault mode, set vault mode, switch to PARA, use LYT, Zettelkasten setup, change mode, configure mode, or methodology routing.…