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 storybrandgit 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/storybrand)<a href="https://agentmods.dev/skills/hirogakatageri/hirokata/storybrand"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/storybrand/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/storybrand"><img src="https://agentmods.dev/badge/skills/hirogakatageri/hirokata/storybrand.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.00124 | $0.01211 |
| Opus 5 | $0.00062 | $0.00606 |
| Sonnet 5 | $0.00025 | $0.00242 |
| Haiku 4.5 | $0.00012 | $0.00121 |
Grade A, and why
storybrand 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
StoryBrand (SB7) — The Customer Is the Hero, You Are the Guide
Donald Miller, Building a StoryBrand. The mistake most brands make is casting themselves as the hero. In every story that works, the hero is the one with the problem — the customer — and the brand plays the guide (Yoda, not Luke) who hands them a plan and calls them to act. "If you confuse, you lose."
The Seven Parts (SB7)
- A Character — the customer, the hero. Open with them and what they want, not with you.
- has a Problem — on three levels:
- External: the tangible obstacle ("my reports take three days").
- Internal: how it makes them feel ("I feel behind and disorganized").
- Philosophical: why it's wrong ("finance teams shouldn't be stuck doing manual work"). Great messaging speaks to the internal problem — that's what people actually buy relief from.
- and meets a Guide — you. Show two things: empathy ("we get it") and authority (proof you can help — results, testimonials, credentials).
- who gives them a Plan — a simple path, usually 3 steps. It removes the fear of "how does this work / what do I have to do?"
- and calls them to Action — one clear, direct call to action (a direct CTA like "Start free" plus optionally a transitional one like "Download the guide"). Heroes don't act unless challenged to.
- that helps them avoid Failure — name the stakes. What's at risk if they don't act? (Use sparingly — a little loss aversion, not fear-mongering.)
- and ends in Success — paint the resolution. Show them the transformed life on the other side.
When to use it (and when not)
Use it for: landing pages, homepages, value propositions, sales and pitch decks, cold emails, ad copy, onboarding, any customer-facing message that needs to convert.
Reach for something else when: the audience is internal leadership deciding (→
pyramid-principle), you're rallying your own team on mission (→ golden-circle), or you just need
a one-line hook (→ abt). StoryBrand is aimed outward, at the buyer.
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 · 91 lines · 124 tokens per session scan A 4f450a5088f0
storybrand is a skill published in the GitHub repository HirogaKatageri/hirokata (5 stars, last pushed 3d ago), licensed MIT. It adds 124 tokens to every session and 1,211 once invoked, about $0.0006 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…