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 sumitaich1998/OpenDate --skill re-engagementgit clone --depth 1 https://github.com/sumitaich1998/OpenDateWrote 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/sumitaich1998/opendate/re-engagement)<a href="https://agentmods.dev/skills/sumitaich1998/opendate/re-engagement"><img src="https://agentmods.dev/badge/skills/sumitaich1998/opendate/re-engagement/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/sumitaich1998/opendate/re-engagement"><img src="https://agentmods.dev/badge/skills/sumitaich1998/opendate/re-engagement.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.00032 | $0.00533 |
| Opus 5 | $0.00016 | $0.00267 |
| Sonnet 5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
re-engagement 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
Re-engagement
Threads stall for a hundred boring reasons — busy weeks, app fatigue, three other chats. A good re-engagement gives them an easy, pressure-free reason to pick the conversation back up. A bad one makes it weird.
Mindset
- Assume good faith, not rejection. People get busy. Lead with lightness.
- One quality attempt, then let go. Send one good re-engagement. If there's still nothing, stop — chasing is never attractive and never allowed.
- Add value, don't extract. Give them something fun to react to instead of demanding attention.
Tactics that work
- The callback hook. Reference your last shared joke or topic with a new twist. ("Update: I went to that ridge trail again purely so I'd have a better photo to show you. Priorities.")
- The relevant nudge. Something in the world reminded you of them — a song, a meme, an event tied to your conversation.
- The light re-opener. A fresh, easy question unrelated to the silence, with zero guilt attached.
- Playful self-aware (sparingly). "Pretty sure I owe the universe a better taco take — got one if you're around."
Hard don'ts
- No guilt trips. "Guess you're busy…", "did I say something?", "helloo??" All off-limits.
- No double/triple texting the same dead thread. One attempt.
- No neediness or negging. Don't perform hurt; don't insult to provoke a reply.
- Don't restart the exact same question they didn't answer — change the hook.
Calibration
- Keep it lighter and lower-stakes than your average message.
- Make it effortless to reply to — and equally fine to ignore.
- If they re-engage with low energy, ease back in gently; don't immediately pile on.
Output
A single, warm, low-pressure message with a fresh hook — no mention of the silence, no guilt — that's genuinely easy and fun to answer.
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 · 55 lines · 32 tokens per session scan A 017568f29e00
re-engagement is a skill published in the GitHub repository sumitaich1998/OpenDate (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 533 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
build-bot-funnel
A workflow that turns a written conversation plan into a validated chatbot flow for Telegram, MAX, or Instagram.
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
make-a-deck
Slide presentation in HTML.
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
subscription-manager
Create and manage scheduled subscription tasks. Use when the user wants to set up recurring reminders, periodic reports, scheduled checks, or any automated tasks that run on a schedule. Supports cron expressions, fixed intervals, and one-time executions.