storytelling

storytelling is a skill for Claude Code from sumitaich1998/OpenDate. It costs 25 tokens per session (539 once invoked), scanned A, original, MIT.

A guide to telling short, relatable personal stories that show personality and invite the other person to share their own experience.

In plain words
What is it for?
It is for writing text-message anecdotes with a hook, an unexpected turn, a meaningful ending, and a question or invitation for the other person.
Why use it?
It helps messages feel more human than a list of facts, while avoiding stories that are too long, irrelevant, or self-promotional.

Skill for Claude Code

Written for Claude Code: when-to-use in frontmatter.

Good fit It is for writing text-message anecdotes with a hook, an unexpected turn, a meaningful ending, and a question or invitation for the other person.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sumitaich1998/opendate/storytelling
Install

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.

Any agent
npx skills add sumitaich1998/OpenDate --skill storytelling
Clone the repo
git clone --depth 1 https://github.com/sumitaich1998/OpenDate

Made for: Claude Code.

Wrote 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.

agentmods badge for storytelling

README.md
[![agentmods](https://agentmods.dev/badge/skills/sumitaich1998/opendate/storytelling/github.svg)](https://agentmods.dev/skills/sumitaich1998/opendate/storytelling)
Your own site
<a href="https://agentmods.dev/skills/sumitaich1998/opendate/storytelling"><img src="https://agentmods.dev/badge/skills/sumitaich1998/opendate/storytelling/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.

agentmods 80×15 button for storytelling

Your own site · 80×15
<a href="https://agentmods.dev/skills/sumitaich1998/opendate/storytelling"><img src="https://agentmods.dev/badge/skills/sumitaich1998/opendate/storytelling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 539 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00539
Opus 5 $0.00013 $0.00269
Sonnet 5 $0.00005 $0.00108
Haiku 4.5 $0.00003 $0.00054

Measured 11d ago against content hash 6b7690cec3ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

storytelling 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

src/opendate/skills/registry/storytelling/SKILL.md · 58 lines

What it actually says

Storytelling

A well-told little story does what a list of facts can't: it shows personality, values, and humor all at once — and it makes them want to tell you one back.

Anatomy of a great text-message story

Keep it to 2–4 sentences. Structure:

  1. Hook — a one-line setup that creates a small question. ("So I once tried to impress a date by cooking and nearly set off the smoke alarm at her place.")
  2. Turn — the unexpected or funny beat.
  3. Landing — a punchline or a small, honest reflection that reveals something about you.
  4. Handoff — invite their version. ("Please tell me you have a worse first-date disaster.")

Choosing the story

  • Relevance over impressiveness. Pick something that connects to what they just said. A relevant small story beats an epic non-sequitur.
  • Reveal a value, not a résumé. The best stories show how you think, what you find funny, what you care about — not how cool you are.
  • Vulnerability in small doses. A little self-deprecation or honesty builds trust. Save the heavy stuff for later/in person.
  • Have a point. End on a punchline or an insight, never just "…anyway."

Delivery on text

  • Front-load the hook; phones reward brevity.
  • Compress ruthlessly — cut everyone who isn't essential to the story.
  • Land, then pass the mic. Always invite their version so it stays a dialogue, not a monologue.
  • Voice matters most here. This is where the user's persona should shine; hand off to persona-style-transfer so the cadence and humor are unmistakably theirs.

Do / Don't

  • Do keep it tight and end with a clear hook back to them.
  • Do let the story reveal character.
  • Don't ramble, brag, or trauma-dump.
  • Don't tell a story with no point or no handoff.

Output

A 2–4 sentence anecdote with a clear landing and an invitation for them to share their own.

Changes

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.

  1. 11d ago First seen · 58 lines · 25 tokens per session scan A 6b7690cec3ac

Subscribe to this mod's changes

storytelling is a skill published in the GitHub repository sumitaich1998/OpenDate (2 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 539 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.

Related

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.

skiddgoddamn/zaytsv-mcp · 137 tokens

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…

aden-hive/hive · 133 tokens

make-a-deck

Slide presentation in HTML.

asgeirtj/system_prompts_leaks · 9 tokens

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.

aden-hive/hive · 40 tokens

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…

shiwenwen/hope-agent · 115 tokens

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.

wecode-ai/Wegent · 49 tokens