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 approachinggit 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/approaching)<a href="https://agentmods.dev/skills/sumitaich1998/opendate/approaching"><img src="https://agentmods.dev/badge/skills/sumitaich1998/opendate/approaching.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.1 | $0.00027 | $0.00524 |
| Opus 5 | $0.00014 | $0.00262 |
| Sonnet 5 | $0.00005 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
approaching 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 8d 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
Approaching
The opener starts the conversation; approaching is how you carry the first few turns so it has somewhere to go. The goal is a relaxed, two-sided rhythm — not an interview, not a performance.
Goals for the first exchanges
- Set a warm, low-pressure tone. You're glad you matched; you're curious; you're easy to talk to.
- Establish reciprocity. They share a little, you share a little. Never take more than you give.
- Find the live thread. Notice which topic gets the most energy and follow it instead of resetting.
Tactics
- Mirror, then add. Acknowledge what they said, then contribute something of your own so they can react. Statements invite more than back-to-back questions.
- Trade, don't interrogate. For every question you ask, offer the answer for yourself too. ("…I'm firmly team mountains, but I could be converted.")
- Calibrate length. Roughly match their message length and effort. If they send one line, don't reply with a paragraph.
- Bring energy up by one notch, not three. Be a touch warmer/more playful than them; let them rise to meet it.
- Use names and callbacks. Referencing something they said two messages ago signals real attention.
Reading the room
- High energy back (emojis, teasing, fast replies) → move toward
banter/flirting. - Thoughtful, slower → lean into
rapport-building. - Short / low effort → ask one genuinely interesting, specific question; if it stays flat, ease off rather than chasing.
Do / Don't
- Do keep it balanced: share, ask, react.
- Do let a good tangent take over.
- Don't fire three questions in a row.
- Don't over-invest before they've invested anything.
Output
The next message in the thread — conversational, balanced, and tuned to their energy. Hand off to the right Building skill once a live thread appears.
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.
- 8d ago First seen · 57 lines · 27 tokens per session scan A 6dde892bd4d5
approaching is a skill published in the GitHub repository sumitaich1998/OpenDate (2 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 524 once invoked, about $0.0001 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…
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.
make-a-deck
Slide presentation in HTML.
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.