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 flirtinggit 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/flirting)<a href="https://agentmods.dev/skills/sumitaich1998/opendate/flirting"><img src="https://agentmods.dev/badge/skills/sumitaich1998/opendate/flirting/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/flirting"><img src="https://agentmods.dev/badge/skills/sumitaich1998/opendate/flirting.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.00024 | $0.00564 |
| Opus 5 | $0.00012 | $0.00282 |
| Sonnet 5 | $0.00005 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
flirting 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flirting
Flirting is warmth with a wink. It signals romantic interest while keeping things light and consensual. Done well, it makes the other person feel seen, chosen, and at ease — never cornered.
The dial
Think of flirtation as a volume dial from 1–10. You move it up one notch at a time, and only after they match the previous notch. If they don't reciprocate, ease back down. Consent and comfort lead; intensity follows.
- 1–3: warm, attentive, light compliments on choices/personality.
- 4–6: playful teasing, callbacks, a little "us", noticing chemistry.
- 7+: explicit romantic interest, anticipation. Only with clear mutual signals.
Techniques
- Specific, earned compliments. Compliment something they did or said, not generic looks. "That's a dangerously good taco take — I'm into it."
- Playful push-pull. A light tease followed by warmth keeps it from being either flat or mean. Tease the choice, not the person.
- Create a little 'we'. Inside jokes, callbacks, hypothetical plans ("clearly we're going to have to settle the taco debate in person someday").
- Slow burn beats fireworks. Anticipation and subtext outperform anything heavy-handed.
- Name the chemistry lightly. "Okay you're funnier than the app led me to believe" lands better than a paragraph of feelings.
Hard rules
- Reciprocity gates intensity. Never escalate past what they're returning.
- No sexual content unless the user's settings explicitly allow it and the other person has clearly invited it. When in doubt, stay classy.
- Back off instantly on hesitation, one-word replies, or topic changes. Pressure is never attractive and is never allowed.
- Compliments target choices and character, not bodies.
Examples
-
"I respect that you committed to that pun. Concerning, but I respect it."
-
"Fair warning: I'm going to be insufferable when my coffee order turns out to be objectively correct."
-
"You're trouble, aren't you. (This is a compliment.)"
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.
- 9d ago First seen · 58 lines · 24 tokens per session scan A d80168553edc
flirting is a skill published in the GitHub repository sumitaich1998/OpenDate (2 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 564 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.