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 HirogaKatageri/hirokata --skill storytellinggit clone --depth 1 https://github.com/HirogaKatageri/hirokataWrote 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/hirogakatageri/hirokata/storytelling)<a href="https://agentmods.dev/skills/hirogakatageri/hirokata/storytelling"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/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.
<a href="https://agentmods.dev/skills/hirogakatageri/hirokata/storytelling"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/storytelling.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.00176 | $0.02385 |
| Opus 5 | $0.00088 | $0.01192 |
| Sonnet 5 | $0.00035 | $0.00477 |
| Haiku 4.5 | $0.00018 | $0.00238 |
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 12d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Storytelling — Pick the Right Frame, Then Make It Land
Most communication fails not because the idea is weak but because it is delivered in the wrong shape. A board wants the answer first; a team wants a reason to care; a customer wants to be the hero. This skill diagnoses the situation, picks the framework that fits, and drafts the message in it — and, when it helps, drafts it several ways at once so you can feel which one lands.
It draws on six battle-tested storytelling frameworks, each strong for a different job:
| Framework | Shape | Strongest for |
|---|---|---|
| Golden Circle (Sinek) | Why → How → What | Rallying a team, brand & vision, "why we exist" |
| Pyramid Principle (Minto) | Answer first → grouped evidence | Boards, execs, investors, decision memos |
| Pixar Pitch (Coats) | Once upon a time → Every day → Until finally | Transformation, journeys, change stories |
| StoryBrand (Miller) | Customer = hero, you = guide | Marketing, sales, landing pages, value props |
| What / So What / Now What | Fact → impact → action | Post-mortems, retros, status, incident reviews |
| ABT (And, But, Therefore) | Setup → tension → resolution | Elevator pitch, one-liner, hook in <30s |
Each framework is also a standalone skill (golden-circle, pyramid-principle, pixar-pitch,
storybrand, what-so-what-now-what, abt) if the user already knows which one they want.
Workflow
Step 1 — Get the raw material (don't over-interview)
You need four things. Take whatever the user gave you and ask, in one short message, only for what's missing:
- The message — what are you actually trying to say? (the idea, ask, update, or point)
- The audience — who receives it, and what do they care about?
- The outcome — what should they think, feel, or do afterward?
- The medium & length — a Slack post? a 2-minute pitch? a keynote? a landing page? one line?
If the user already made these clear, skip the questions and go straight to Step 2.
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.
- 12d ago First seen · 167 lines · 176 tokens per session scan A 9d61dc8faa59
storytelling is a skill published in the GitHub repository HirogaKatageri/hirokata (5 stars, last pushed 3d ago), licensed MIT. It adds 176 tokens to every session and 2,385 once invoked, about $0.0009 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
unslop
Humanize LLM output so it reads like a careful human wrote it. Subtracts AI-isms (sycophancy, tricolons, em-dash overuse, "delve"/"tapestry"/"testament", hedging stacks, tidy five-paragraph shapes), engineers burstiness and calibrated uncertainty, and preserves technical accuracy. Supports intensity levels: subtle…
unslop-file
Humanize natural-language memory files (CLAUDE.md, todos, preferences, docs) by removing AI-isms and adding burstiness while preserving every code block, URL, path, command, and heading exactly. Two modes: --deterministic (fast, regex-based, no API) and LLM (default, calls Claude for rewrite). Humanized version…
unslop-commit
Rewrites commit messages so they sound like a careful human engineer wrote them. Strips AI/marketing slop ("comprehensive solution", "robust implementation", "leverage", "enhance", "seamlessly", "This commit..."). Keeps Conventional Commits format. Subject ≤72 chars (aim ≤50), imperative mood. Body only when "why"…
unslop-help
Quick-reference card for unslop modes, sub-skills, and slash commands. One-shot display, not a persistent mode. Trigger: /unslop-help, "unslop help", "what unslop commands", "how do I use unslop".
simulator-charts
Simulator.Company chart and dashboard specialist. Use when the user wants to create, configure, or query charts (line, bar, area), dashboards, or financial time-series visualisations on a graph layer. Trigger on any of these intents: — Creating: "create chart", "add chart", "create dashboard", "add dashboard", "build…
simulator-init
Simulator.Company environment setup specialist. Use when the user wants to connect to Simulator.Company, set up credentials, authenticate, configure the workspace, or start working with Simulator for the first time. Activate when the user says "init", "setup", "connect to simulator", "login to simulator", "configure…