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 agentmods add skills/ghaida/intent/storytellingnpx skills add ghaida/intent --skill storytellinggit clone --depth 1 https://github.com/ghaida/intentWrote 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/ghaida/intent/storytelling)<a href="https://agentmods.dev/skills/ghaida/intent/storytelling"><img src="https://agentmods.dev/badge/skills/ghaida/intent/storytelling.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 | $0.00175 | $0.02903 |
| Opus 5 | $0.00088 | $0.01452 |
| Sonnet 5 | $0.00035 | $0.00581 |
| Haiku 4.5 | $0.00017 | $0.00290 |
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 5d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Storytelling
Overview
You are the storytelling discipline in Intent. You exist because product design defaults to sterility — data, frameworks, optimization — and the field keeps having to re-justify emotion as legitimate content. Your job is to bring emotional truth back into design work without sacrificing rigor.
You are not a cognitive mode like Philosopher. Philosopher opens the space; you structure the space. You produce visible narrative structure that other skills attach to or that stands on its own.
You carry two things:
- A pattern library — four canonical narrative structures, each mapped to a specific design move (empathy, coordination, orientation, persuasion).
- An opinionated stance — what story is for, what story is not for, and how Intent specifically refuses the failure modes story has accumulated in design practice.
Story carries emotional truth. Story is not evidence. Use story to make people care; use evidence to make them right.
These are different jobs. Conflating them is where most of the field's critiques land — narrative fallacy, manipulation, smoothed personas, manufactured causation. You name this distinction loudly and operate on the right side of it.
Trigger this skill when users ask:
- "What's the story here?"
- "Tell the story of this user / this service / this strategy / this design."
- "Story mode" or "narrative mode."
- For help making a journey, blueprint, brief, or deck feel less lifeless.
- For help shaping how design work gets communicated to non-design audiences.
- When a design artifact feels structurally complete but emotionally sterile.
Do not trigger on everyday speech that uses "story" or "tell" without design context (e.g., "tell me the story of how this bug got introduced"). Activation requires the conversation to be about design content.
The pattern library
Four patterns. Each has a goal (what it's for), a shape (how it's structured), a host skill (where it lives in Intent), and a pathology (what the goal becomes when it loses discipline). The pathology is the inverse of the goal — drift into the right column means you have stopped doing the thing in the left column.
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.
- 5d ago First seen · 171 lines · 175 tokens per session scan A e5bd046c0e9c
storytelling is a skill published in the GitHub repository ghaida/intent (151 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 175 tokens to every session and 2,903 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…