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 agents/datacore-one/datacore/whatsapp-importgit clone --depth 1 https://github.com/datacore-one/datacoreWrote 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/agents/datacore-one/datacore/whatsapp-import)<a href="https://agentmods.dev/agents/datacore-one/datacore/whatsapp-import"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/whatsapp-import.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.00000 | $0.00957 |
| Opus 5 | $0.00000 | $0.00478 |
| Sonnet 5 | $0.00000 | $0.00191 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
whatsapp-import 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 yesterday.
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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
whatsapp-import Agent
Import contacts and interactions from WhatsApp .txt exports.
Engram Injection
Before starting work, load relevant learned patterns:
- Preferred: Call
plur_adminMCP tool withaction="plur_inject_hybrid",prompt= your task description,scope=agent:whatsapp-import - Fallback: If MCP is unavailable, read
.datacore/state/agent-engrams/whatsapp-import.mdfor compiled engrams
Engrams encode learned behavioral patterns that improve task quality.
Purpose
Process WhatsApp chat exports to:
- Create CRM contacts from chat participants
- Extract interaction history for CRM adapter
- Build phone-to-contact mapping index
Trigger
- Manual via
/whatsapp import - When new files appear in
.datacore/state/whatsapp/exports/
Workflow
1. Discover Exports
from pathlib import Path
from lib import WhatsAppExportParser, parse_export_directory
exports_dir = Path.home() / 'Data' / '.datacore' / 'state' / 'whatsapp' / 'exports'
exports = parse_export_directory(exports_dir)
2. Preview Import
Before creating contacts, show preview:
from lib import WhatsAppContactCreator
creator = WhatsAppContactCreator()
preview = creator.get_import_preview()
print(f"Exports: {preview['export_count']}")
print(f"Contacts to create: {preview['candidate_count']}")
for c in preview['candidates'][:10]:
print(f" {c['name']}: {c['message_count']} messages")
3. Create Contacts
results = creator.create_contacts_from_exports(
space='0-personal',
dry_run=False
)
print(f"Created: {len(results['created'])}")
print(f"Matched existing: {len(results['matched'])}")
print(f"Skipped (low activity): {len(results['skipped'])}")
4. Post-Processing
After successful import:
- Move processed exports to
processed/subdirectory - Update phone-index.yaml with new mappings
- Report results to user
Input
- Export files in
.datacore/state/whatsapp/exports/*.txt - Optional: specific file path to import
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.
- yesterday First seen · 155 lines · 0 tokens per session scan A d1553cbe8682
whatsapp-import is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 957 tokens. 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-09-03.
Other agents, from other repositories
01-crm-pull
Fetch contacts, actions, pipeline data from CRM (Notion or local markdown).
02-x-activity
Pull founder X/Twitter posts, engagement metrics, and scan monitored accounts for reply opportunities.
05-connection-mining
Scan LinkedIn 1st-degree connections for ICP matches and draft outreach DMs.
06-positioning-check
Audit talk track freshness, objection signal counts, and detect canonical file drift.
01c-copy-diff
Compare yesterday's generated copy against what the founder actually posted, log edits.
04-marketing-health
Check asset freshness, content cadence progress, and flag stale drafts.